aah, of course, never mind, my bad. it came from the local userland repo i.e.
my testbuild.
all good, just ignore me :-P
i'll go ahead with the new version then, even if it's still using openssl
1.0.2. it would at least
be the current one.
On Tue, 4 Jun 2024 20:56:07 +0200, Andreas Wacknitz vi
Am 04.06.24 um 17:57 schrieb Goetz T. Fischer:
On Tue, 4 Jun 2024 11:24:28 +0200, Till Wegmüller wrote:
Hi Goetz
No that can happen if somehow your local userland-incorporation is out
of date becasue it could not update some packages.
it updated fine. my local pkg update was fine. what was out
On Tue, 4 Jun 2024 11:24:28 +0200, Till Wegmüller wrote:
> Hi Goetz
>
> No that can happen if somehow your local userland-incorporation is out
> of date becasue it could not update some packages.
it updated fine. my local pkg update was fine. what was out of date is the repo
website.
__
Hi Goetz
No that can happen if somehow your local userland-incorporation is out
of date becasue it could not update some packages.
What usually solves this for me:
- Remove all locally installed versions of packages (all that have the
userland publisher)
- Force an install of the not installe
