Porteus Roadmap

[rych]

Is Porteus 5.0 RC3 going to be updated one day? Or should I start learning APorteus instead?

(I'm beginning to be disturbed by growing incompatibilities. Nowadays quickly getting a simple package like xdpyinfo through getpkg which used to give an oldish but immediately working module, produces a package that is ahead, complaining about GLIBC mismatch etc.)

[ncmprhnsbl]

.. very soon ..hopefully before the end of this month

(I'm beginning to be disturbed by growing incompatibilities. Nowadays quickly getting a simple package like xdpyinfo through getpkg which used to give an oldish but immediately working module, produces a package that is ahead, complaining about GLIBC mismatch etc.)

in the meantime, for rc3 getpkg, i suggest editing /usr/local/bin/getpkg line 31 to:

Code: Select all

SLACKVER=15.0

(instead of current) .. this should lessen 'older library' issues( though perhaps not eliminate entirely)

[babam]

.. very soon ..hopefully before the end of this month

Good news

[Ed_P]

hopefully before the end of this month

5.0rc4?

[babam]

5.0rc4?

I hope it's a stable version, too many rc releases.

[ncmprhnsbl]

5.0rc4?

no more RCs

[Ed_P]

no more RCs

[kultex]

May is already over and June too - when will it be? hopefully soon ...

[rych]

An interesting date is approaching, the 8th of July: exactly one year since the celebrated Porteus-v5.0rc3 was released

[babam]

I'm surprised Porteus 5.0 stable will use glibc-2.35

[Karmi]

An interesting date is approaching, the 8th of July: exactly one year since the celebrated Porteus-v5.0rc3 was released

That sounds like a date wid some serious Juju to it...

[rych]

this should lessen 'older library' issues( though perhaps not eliminate entirely)

Indeed the SLACKVER=15.0 helped some, thank you. But for example

Code: Select all

root@porteus:~# getpkg pavucontrol
...
Creating /tmp/pavucontrol-5.0-x86_64-1.xzm
...
root@porteus:~# pavucontrol 
pavucontrol: /usr/lib64/libstdc++.so.6:version `GLIBCXX_3.4.29' not found
(required by pavucontrol)

So both GLIBC and GLIBCXX have to match, so in this case where would I find the lucky pavucontrol? Had to use the old pavucontrol-3.0-x86_64-bundle.xzm from 2020.

[babam]

Code: Select all

root@porteus:~# pavucontrol 
pavucontrol: /usr/lib64/libstdc++.so.6:version `GLIBCXX_3.4.29' not found

Check this out libstdc++.so.6 - Resolve the error message (Post by Rapha_ #85565)

[rych]

babam, Thanks but still:

Code: Select all

root@porteus:~# pavucontrol 
pavucontrol: symbol lookup error: pavucontrol: undefined symbol: pa_context_send_message_to_object, version PULSE_0

Anyway maybe it's not worth it to fix this now, better wait for the upcoming Porteus release. I was just mentioning it in this thread to add to the list of problems that lagging behind (even) Slackware may cause, so that our developers feel the motivation

(By the way, this forum engine is also broken -- whenever I want to post I have to clear its cookies first)

[Ed_P]

(By the way, this forum engine is also broken -- whenever I want to post I have to clear its cookies first)

I have problems logging in, linux and windows, but no problem with cookies on either system.