SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I think they means any package that can use Python 3.x should be built against Python 3.x. While a good case can be made for that, there are some packages known to have issues when defaulting against Python 3.x. Python 2.x is still the default for many packages, so generally, until Python 3.x is the default and Python 2.x is the option, the defaults should stay as-is for sanity in packages and dependencies.
cause 2.x and 3.x series can coexist in same system...then the way is, when python3 arrives as a default slackware package.
not python2 or python3 // two better tan one.
If Slackware ships both, then I want every Python library that it ships (PyQt, PyGTK, etc) to be built for both.
I'd prefer is Slackware holds off shipping Python 3 until it's ready to make it the standard. (And honestly, I think that can happen by the next release after 14.2).
Tue Jun 7 21:39:07 UTC 2016
a/smartmontools-6.5-x86_64-1.txz: Upgraded.
n/gnutls-3.4.13-x86_64-1.txz: Upgraded.
Use secure_getenv() where available to obtain environment variables to
fix an issue where setuid programs could potentially allow an attacker
to overwrite and corrupt arbitrary files.
This issue was only present in gnutls-3.4.12.
For more information, see: http://cve.mitre.org/cgi-bin/cvename...=CVE-2016-4456
(* Security fix *)
n/samba-4.4.4-x86_64-1.txz: Upgraded.
Migrate any .tdb files in /etc/samba/private to /var/lib/samba/private.
Thanks to ivandi.
xap/gkrellm-2.3.7-x86_64-1.txz: Upgraded.
xap/mozilla-firefox-45.2.0esr-x86_64-1.txz: Upgraded.
This release contains security fixes and improvements.
For more information, see: http://www.mozilla.org/security/know...irefoxESR.html
(* Security fix *)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.