libexpat.so.14.0 missing in latest -current

[Anthony Campbell]

After upgrading to -current today I found that xenodm would not run
because of a missing /usr/lib/libexpat.so.14.0_ Various other things
didn['t work either, including vim.

As a temporary work-round I made a link for it to libexpat.so.13.0,
which seems to have made everything function again.

[Matthias Schmidt]

Hi,

Post by Anthony Campbell
After upgrading to -current today I found that xenodm would not run
because of a missing /usr/lib/libexpat.so.14.0_ Various other things
didn['t work either, including vim.

Had the same. Just fetch latest sets again and all is working.
ftp.hostserver.de has the latest sets with the new libexpat.

Cheers

Matthias

[Anthony Campbell]

Post by Matthias Schmidt
Hi,

Post by Anthony Campbell
After upgrading to -current today I found that xenodm would not run
because of a missing /usr/lib/libexpat.so.14.0_ Various other things
didn['t work either, including vim.

Had the same. Just fetch latest sets again and all is working.
ftp.hostserver.de has the latest sets with the new libexpat.
Cheers
Matthias

Yes, I found another snapshot later the same day and this
provided the missing item.

Thanks,

Anthony

[Theo de Raadt]

Post by Anthony Campbell
After upgrading to -current today I found that xenodm would not run
because of a missing /usr/lib/libexpat.so.14.0_ Various other things
didn['t work either, including vim.
As a temporary work-round I made a link for it to libexpat.so.13.0,
which seems to have made everything function again.

Occasionally a bad snapshot will ship out, because we are actively
developing. It is rare. Shrug.

[Christer Solskogen]

Post by Theo de Raadt
Occasionally a bad snapshot will ship out, because we are actively
developing. It is rare. Shrug.

And OpenBSD even has some awesome tools to discover this, so it's really
not a big problem and that tool is vmm.
I have a VM that I upgrade first. If that goes swell, my primary and backup
firewall gets the upgrade.