--l8yJEXo8J9fv7OFY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Jul 11, 2014 at 01:50:37PM +0200, geoffroy desvernay wrote:
> On 07/10/2014 14:18, Glen Barber wrote:
> > On Thu, Jul 10, 2014 at 01:58:40PM +0200, geoffroy desvernay wrote:
> >> On 07/10/2014 13:20, Glen Barber wrote:
> >>> On Thu, Jul 10, 2014 at 12:59:33PM +0200, geoffroy desvernay wrote:
> >>>> On 07/06/2014 23:54, Glen Barber wrote:
> >>>> After upgrading from 9.3-RC1, sshd refuses to launch with:
> >>>> /usr/sbin/sshd: Undefined symbol "ssh_explicit_bzero"
> >>>>
> >>>
> >>> I have just installed 9.3-RC1 in a VM, and have verified that
> >>> ssh_explicit_bzero does exist in /usr/lib/private/libssh.so.
> >>>
> >>> What version were you running before upgrading to 9.3-RC1?
> >>>
> >>> Glen
> >>>
> >> 9.2-RELEASE-p7
> >>
> >> I managed to get it working by tar -C/ -xvpf base.txz from 9.3-RC3 rel=
ease
> >>
> >=20
> > I am not sure what happened in your case, but an upgrade from
> > 9.2-RELEASE-p10 to 9.3-RC1 then to 9.3-RC3 also does not show this
> > behavior.
> >=20
> > Glen
> >=20
(Sorry, just saw your reply now.)
> So it's shurely an error of mine :(
>=20
> Could an unfinished upgrade (eg: missing last 'install' after reboot)
> lead to this situation ?
I suppose it is possible, however sshd(8) is linked against
/usr/lib/private/libssh.so, not /usr/lib/libssh.so after the userland
bits are installed.
> Could the next 'fetch' soft-fail indicating that there are uninstalled
> updates ?
>=20
Generally, no. freebsd-update does not really care what version you are
running when upgrading, and would install any updates to the latest
point anyway.
> Here I clearly missed something, but couldn't freebsd-update catch this
> between kernel install and userland to avoid future inconsistent upgrade ?
>=20
In think it already does. But in this case, it would not matter because
the ssh_explicit_bzero is a symbol in a userland shared library, not
part of the kernel.
> (This machine have been installed on 9.1 from binaries, and only
> freebsd-update'ed since)
>=20
Yes, this is why I tested the upgrade path from 9.2-RELEASE through
9.3-RC1 then to 9.3-RC3, in case there was an incompatibility somewhere
earlier.
Glen
--l8yJEXo8J9fv7OFY
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJTwBofAAoJELls3eqvi17QS0UP/2/fawI4LA0GRcJW/Ky3zRwe
H5hEEqYEPGP+34vJBpu9neR5aDSIQoKYmjJxP/SC1U3btw9pMIkLfIQ/UfwWjBUA
DIN9jr/IIeZv1hP34XPdEv2uii3iTIuU4nVfaMRN9hOQH4jg9FrnURSlIfYb89y/
8tFIz9E6859c+tMQJbjigLtTOLAcq+GugRJM5CLE54iNUdwXwh54TmpxHRH3CrnX
nCCbgNo9nSv4pCJxRUizwiK5W7ADF/tOR94q2/Tx3MN6WNpPbf+kRbt3LBARoB++
3rgdTae3v3QcNeGC6oPr295TcIh5AIGmHIluh69XeTHJ1iLJIgGu9xpvcnVw2G6q
S54lFrmaqOa/h79Mt2K+JmQueDKaNgIF+goGpmmCf/7clM00OCrHYC9bGTDUNMCd
cNqn88iRNqGZIbe956pGb91xBzuDtxdj7xg0wgen3kGUjRczWkizzrU6DsnqGU5r
xLkMmrU8KZaqkAAOy+LkPFHgS4S2Fxm5q1so9doi8liLb+eUanVGWUZlcazL4JAS
qykbm5bOslf/57XzksZ5W3SyYdRAyAMLlBJG+xfQIihMyXVmvVKB/AKV8ijQcyaC
EogdaRomJ9B5eQbdM3m5zkgb9vVSS7UicTtkLl574p+Pb8YJBYZP8LA/doGxcVGZ
KRDRhpukRMmX1SavNwG+
=9ARf
-----END PGP SIGNATURE-----
--l8yJEXo8J9fv7OFY--