[SOLVED] Requests for -current (20151216)

gmgf · 09-26-2017, 08:30 AM

mpg123-1.25.7:

https://mpg123.org/
https://mpg123.org/download/mpg123-1.25.7.tar.bz2

lftp-4.8.2:

http://lftp.tech/news.html
http://lftp.yar.ru/ftp/lftp-4.8.2.tar.xz

sanjioh · 09-26-2017, 05:28 PM

terminus font 4.46

montagdude · 09-26-2017, 09:00 PM

I don't want to come across as pushy or start a debate, but I also would like to make sure Pat knows I think we should have have Qt5 and Plasma 5 in the next release. In other words, if you are looking for a show of hands before doing that, mark me down as in favor.

gmgf · 09-27-2017, 01:37 AM

Quote:

Originally Posted by montagdude

I don't want to come across as pushy or start a debate, but I also would like to make sure Pat knows I think we should have have Qt5 and Plasma 5 in the next release. In other words, if you are looking for a show of hands before doing that, mark me down as in favor.

I have already posted (maybe it's time to put qt5 in current, here)

gmgf · 09-27-2017, 02:14 AM

xfsprogs-4.3.1:

https://www.kernel.org/pub/linux/uti...-4.13.1.tar.xz

openvpn-2.4.4:

https://community.openvpn.net/openvp...gesInOpenvpn24
https://swupdate.openvpn.org/communi...n-2.4.4.tar.xz

gmgf · 09-27-2017, 08:13 AM

dbus-1.10.24:

(dbus.expat222fix.diff.gz is applied in this new version)
https://cgit.freedesktop.org/dbus/dbus/log/?h=dbus-1.10
https://dbus.freedesktop.org/release...1.10.24.tar.gz

atelszewski · 09-27-2017, 11:23 AM

Hi,

Something to pay attention to.
What is /usr/bin/python going to point at in the next release?

--
Best regards,
Andrzej Telszewski

orbea · 09-27-2017, 11:45 AM

Right now its pointing to python2.

Code:

$ ls -l /usr/bin/python
lrwxrwxrwx 1 root root 9 Sep 23 19:14 /usr/bin/python -> python2.7

Its trivial for anyone that wants to use python3 to use the /usr/bin/python3 executable, but it would not be trivial to update all the build scripts accordingly if /usr/bin/python suddenly pointed to /usr/bin/python3. As long as python2 continues to be supported and widely used I think there is no harm in leaving it as is.

Didier Spaier · 09-27-2017, 11:46 AM

Quote:

Originally Posted by atelszewski

Hi,

Something to pay attention to.
What is /usr/bin/python going to point at in the next release?

--
Best regards,
Andrzej Telszewski

Here (Slint with Python3 from Salix added):

Code:

 didier[~]$ ls -l /usr/bin/python*
lrwxrwxrwx 1 root root     9 sept. 23 15:30 /usr/bin/python -> python2.7
lrwxrwxrwx 1 root root    14 sept. 23 15:30 /usr/bin/python-config -> python2-config
lrwxrwxrwx 1 root root     9 sept. 23 15:30 /usr/bin/python2 -> python2.7
lrwxrwxrwx 1 root root    16 sept. 23 15:30 /usr/bin/python2-config -> python2.7-config
-rwxr-xr-x 1 root root  6184 sept. 21 21:28 /usr/bin/python2.7
-rwxr-xr-x 1 root root  1681 sept. 21 21:28 /usr/bin/python2.7-config
lrwxrwxrwx 1 root root     9 sept. 23 15:29 /usr/bin/python3 -> python3.5
lrwxrwxrwx 1 root root    16 sept. 23 15:29 /usr/bin/python3-config -> python3.5-config
-rwxr-xr-x 2 root root 10336 août  30 11:43 /usr/bin/python3.5
lrwxrwxrwx 1 root root    17 sept. 23 15:29 /usr/bin/python3.5-config -> python3.5m-config
-rwxr-xr-x 2 root root 10336 août  30 11:43 /usr/bin/python3.5m
-rwxr-xr-x 1 root root  3079 août  30 11:43 /usr/bin/python3.5m-config

So here /usr/bin/python => python2.

This being said I don't know if you will have something similar in Slackware-current, that I don't run at the moment.

You have to tell explicitly that you want the binary python3. As a reminder there are several ways to do that when building a package.

For instance for brltty: PYTHON=/usr/bin/python3 ./configure ...

But for pyatspi: ./configure --with-python=/usr/bin/python3 ...

EDIT orbea was faster...

dugan · 09-27-2017, 01:17 PM

Quote:

Originally Posted by orbea

As long as python2 continues to be supported and widely used I think there is no harm in leaving it as is.

Python 2 EOLs in 2020, same year as Flash.

That should be an interesting year...

USUARIONUEVO · 09-27-2017, 01:40 PM

Arround qt5 and plasma5 , i read plasma project make end cycle to port pending qt4 apps to qt5 kf5 in the end of 2017

Then , probably is better start frameworks in december to no depending on a kde4/libs package for some apps.

USUARIONUEVO · 09-27-2017, 01:52 PM

If think in perl

5.26.1 , there is a CVE security issue

https://cve.mitre.org/cgi-bin/cvenam...=CVE-2016-2381

and there is the patch
https://git.archlinux.org/svntogit/p...=packages/perl

USUARIONUEVO · 09-27-2017, 03:59 PM

Cython-0.27
https://pypi.python.org/packages/94/...on-0.27.tar.gz

Darth Vader · 09-27-2017, 04:05 PM

Quote:

Originally Posted by USUARIONUEVO

Arround qt5 and plasma5 , i read plasma project make end cycle to port pending qt4 apps to qt5 kf5 in the end of 2017

Then , probably is better start frameworks in december to no depending on a kde4/libs package for some apps.

Code:

                                  ---> KDE Plasma 5 ---> ?
                                  |
                                  |
KDE -> KDE2 -> KDE3 -> KDE(SC)4 --|---> KDE Frameworks 5 ---> ?
                                  |
                                  |
                                  ---> KDE Apps ---> ?

How about NOPE?

I for one, I want to run Slackware, not Plasmaware!

USUARIONUEVO · 09-27-2017, 05:02 PM

kde2 --> kde3 --> kde4 --> kde5

or kde4 no have separated libs package , apps package etc etc ?

return to kde1 if you want.