Re: libexpat.so.14.0 missing in latest -current

[Anthony Campbell]

On 27 May 2021, Matthias Schmidt wrote:
> Hi,
> 
> * Anthony Campbell wrote:
> > 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

-- 
Anthony Campbellhttps://www.acampbell.uk

Re: libexpat.so.14.0 missing in latest -current

[Christer Solskogen]

On Thu, May 27, 2021 at 4:53 PM Theo de Raadt  wrote:

> 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.

-- 
chs

Re: libexpat.so.14.0 missing in latest -current

[Theo de Raadt]

Anthony Campbell  wrote:

> 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.

Re: libexpat.so.14.0 missing in latest -current

[Matthias Schmidt]

Hi,

* Anthony Campbell wrote:
> 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