On 2025-07-19, Michael Joy <michaeljo...@protonmail.com> wrote: > --b1=_2ngZBRzU5QvOmksSDzxuwCkKxfQN9IkwPmPbrzFaCU8 > Content-Type: text/plain; charset=utf-8 > Content-Transfer-Encoding: quoted-printable > > Did a sysupgrade yesterday and since then I can't open ungoogled-chromium o=
as mentioned recently, https://marc.info/?l=openbsd-misc&m=175283513932032&w=2 : I recommend deferring updates if there has just been a bump to a shared : library major version for things like libc or libpthread in base (or a : perl update, if you use perl packages) - wait for new packages built : against the new libraries first. (To check, download the tgz for : something linking against the relevant library - I often use moo : because it's small - and check the @wantlib lines in +CONTENTS). (-current snapshots are really best used by people who are keeping track of developments - reading the cvs changelog is advisable, either via the source-changes mailing list, or fetching CVSROOT from one of the reposync mirrors listed on https://www.openbsd.org/anoncvs.html and running e.g. logtail on CVSROOT/ChangeLog. if this seems too much like hard work then sticking to releases rather than snapshots might be a good idea). ... however, for the current issue, new packages are now available on amd64 i386 sparc64, and updating should fix things - aarch64 should follow fairly soon.
