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
hi guys,
i was about to update libssh2 despite the lack of openssl > 1.0.2 support and
checked:
http://pkg.openindiana.org/hipster/en/search.shtml?token=libssh2&action=Search
there i saw "library/libssh2@1.10.0,5.11-2023.0.0.2:20230917T073330Z". still
the old one so i fired
up my userland vm
unfortunately libssh2 turned out to be yet another ssl mediator victim. however
this one can
probably be solved because it builds fine. the problem only occurs during
publish:
/userland/oi-userland/components/library/libssh2/build/manifest-i386-libssh2.depend
has unresolved
dependency '
d
Hi, Goetz
I am not aware of any compatibility issues if there are it would be a
good idea to remove them. Best way to find out is to start and push it
through the finishline.
-Till
On 14.05.24 03:52, Goetz T. Fischer wrote:
hi guys,
just a quickie, i've been going through the list of packa
hi guys,
just a quickie, i've been going through the list of packages with security
implications and noticed
that libssh2 is at 1.10.0. however 1.11.0 has been released almost one year ago
so i wondered, is
that on purpose because of some compatibility issues or something like that?
if not i w
