SliTaz Forum

Ceel

Administrator

Registered: 2011-04-02

Posts: 1,424

Maybe you shouldn't update your SliTaz

Tazpkg doesn't work in Rolling as in Current. After that [c]libcrypto[/c] will be updated to 3.5.3, [c]tazpkg[/c] won't be able to update any packages.

shann

Administrator

Registered: 2011-04-01

Posts: 1,296

Website

Re: Maybe you shouldn't update your SliTaz

Hi Ceel,

I doing test on qemu with rolling iso i have (january 2025), seem ok when i use [c]tazpkg up -r[/c] in terminal, it's also ok when i use tazpanel to do upgrade packages.

I know tank have unfortunately sporadic issue, last time lighttpd was killed due of many requests

Normally "mirror.slitaz.org" domain not redirect to https for backward compat in old releases.

Agree with you, compare to current, tazpkg on cooking don't fetch all packages before perform upgrade.

of course bad think, if you have this issue, could be happen to other users and break updates/packages consistency

Ceel

Administrator

Registered: 2011-04-02

Posts: 1,424

Re: Maybe you shouldn't update your SliTaz

Hello shann,

Sorry for the very short message, I didn't have many time. I was updating a frugal install and I can reproduce the prolem. Tazpkg always stops to connect to the mirror after it has updated [c]libcrypto[/c]. But I use https://mirror1.slitaz.org/packages/cooking/ ...

If someone has broken his system it's possible to fix it:

from a functional system, download the 3 packages [c]libcrypto[/c], [c]libssl[/c] and openssl;

copy them in your home directory;

open a terminal and become root and

[c]tazpkg -gi libcrypto-3.5.3.tazpkg --forced

tazpkg -gi libssl-3.5.3.tazpkg --forced

tazpkg -gi openssl-3.5.3.tazpkg --forced[/c]

Now, tazpkg works.

But I wonder if it wouldn't be better for the moment to block these 3 packages (and enventually their [c]-dev[/c] in the chroot) before updating because several packages ([c]cups[/c], [c]curl[/c], [c]lynx[/c], ...) depend of them and haven't been rebuilt with the new version.

I can see in the wok that Pascal Bellard tryed to build [c]openssl10[/c], [c]libcrypto10[/c] and [c]libssl10[/c] but cook failed for [c]openssl10[/c]

shann

Administrator

Registered: 2011-04-01

Posts: 1,296

Website

Re: Maybe you shouldn't update your SliTaz

Hi Ceel,

no problem, thanks for clarify, it's my fault also i didn't test with https url for mirror .

Infact it's break tazpkg if mirror url use https.

As you said workaround it's to fetch 3 packages and install them to fix it.

For error on openssl10, i check not really failed, quick search same indicate that error about DSO libprovides.so related to both version of openssl and clash in openssl.conf.

https://mta.openssl.org/pipermail/openssl-users/2022-October/015525.html

Also i see that openssl10 / openssl use same space, if you installed openssl10 you override openssl binary and few file on /etc/ssl include openssl.cnf.