01:27:52 <x0x17> REPENT FOR THE TIME IS AT HAND ... .
01:28:27 <x0x17> LET THE BRIDE SAY COME , THOSE WHO ARE WORTHY LET THEM BE WORTHY STILL ... .
14:07:47 <fenix> Release r151054 (LTS/stable) is available - https://omnios.org/article/r54
20:53:58 <Guest31> Hi. I have just finished a second attempt to upgrade from 046 to 054. Both times re-attaching an ipkg NGZ failed, remainig "configured" rather than becoming "installed". I am aware of the SSL-3 bump and all the affected zones had been upgraded. No data lost, and all affected zones re-attached to the 046 GZ without issue. I'm missing something here,
20:53:58 <Guest31> what might it be?
21:04:14 <Guest5> I upgraded my system from '046 to '054 but I didn't detach my ipkg zones. I just updatedt the publishrs from the global and thndid a "pkg -R /zone/root update" on them once I was back up.
21:05:17 <andyf> Detach/attach is supposed to work. I wonder what's going on.
21:49:52 <Guest31> I have made a mistake. Just checked an image I took with my phone before the rollback. The status of the NGZ was indeed "installed" but 'zoneadm -z alexandria boot' returned that the zone's path can not be mounted using mount -F zfs. "Use 'zfs set mountpoint=/spool/alexandria/root' instead". Specific error was "ERROR: Unable to mount the zone's ZFS
21:49:52 <Guest31> dataset." It suggests that I use 'zfs set mountpoint=legacy'. Apologies for my mistake, my eyes are raisins.