s Wacknitz via oi-dev wrote:
> 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
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.
__
up my userland vm and did a pkg update. to my surprise i spotted:
openindiana.org -> userland
library/libssh2
1.10.0-2023.0.0.2 -> 1.11.0-2024.0.0.0
so is pkg.openindiana.org out of sync or something?
On Thu, 16 May 2024 06:01:04 +0200, Goetz T. Fischer wrote:
> unfortunately li
; 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,
>>
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
On Fri, 19 Apr 2024 18:48:02 +0200, Till Wegmüller wrote:
>> mongodb
>> would have to be updated to at least 6.0.7 for ssl 3 support.
> Which would be good since 4.4 is EOL end of October anyway
according to their website the eol date for 4.4 was even february. october eol
is 5.0.
> In Place it
a few updates here ...
i've been going through the list and picked the ones which are reachable from
the outside first but
also gave gftp a try. gftp and rsync turned out to be cases which don't take
openssl 3 by just
settings the usual as well as specific environment variables and don't offer
On Sun, 25 Feb 2024 17:22:16 +0100, Till Wegmueller wrote:
> 1. Old Packages with newer versions available in the repo.
> In this case this will be solved if/when we do the next repo cleanup.
> (You could also clean them out of your list, we can ignore those)
good.
> 2. Packages not being able to
yes, going with 3.0 is the best choice. but i guess that ship has sailed for
indiana already.
On Sat, 24 Feb 2024 13:33:53 -0800, Alan Coopersmith wrote:
> While OpenSSL now
> promises that all later 3.x versions will be backwards compatible with 3.0,
> they are also promising a longer support li
On Sat, 24 Feb 2024 19:23:33 +0100, Marcel Telka wrote:
> Hi,
>
> On Sat, Feb 24, 2024 at 06:27:30PM +0100, Goetz T. Fischer wrote:
>> as you know there're still some packages in the repo that use openssl 1.0.2.
>> so
>> far this had the unpleasant implication
sure, external mysql libs are not supported anymore but mysqlnd is. that has
been the default for years anyway.
On Sat, 24 Feb 2024 19:04:58 +0100, Friedrich Kink wrote:
> https://php.watch/versions/8.2/mysqli-libmysql-no-longer-supported
>
> Am 24.02.2024 um 18:43 schrieb Goetz T
hello mr. fritzkink,
in regards to this
https://openindiana.org/pipermail/openindiana-discuss/2024-February/026815.html
and assuming you're on this list, just out of couriosity, why did you remove
mysqli.so from php-82 ?
--
R-A-C
Götz T. Fischer CertIT&Comp
+49(0)7225/98 98 79
g.fisc...@r-a-c
the list ...
ssl102_deps.xz
Description: Binary data
___
oi-dev mailing list
oi-dev@openindiana.org
https://openindiana.org/mailman/listinfo/oi-dev
hey all,
as you know there're still some packages in the repo that use openssl 1.0.2. so
far this had the unpleasant implication that all new packages had to be
hardcoded to newer ssl versions one way or the other, because the buildsystem's
ssl mediator had to remain at 1.0.
obviously that wast
14 matches
Mail list logo
