Earlier today, there was a massive update to Slackware-current. The ride was fun, and I am fairly certain we’ll see some breakage. In fact, we found some already and fixed that in a quick update (mounting of Samba shares was broken after splitting the mount utility for Samba shares into its own “cifs-utils” package).
So, what was updated? The highlights of this batch are:
- the version of the next release is known: it will be “Slackware 14”.
- kernel is now 3.2.21 – we will likely stick with the 3.2 series since that will get long-term support.
- KDE moved up to 4.8.4 (meaning that I can remove my own packages for that version from my ktown repository).
- gcc was bumped to 4.7.1 to accompany the new kernel.
- glibc was patched to fix a regression
- python got updated to 2.7.3 (the switch from the old 2.6.x version meant that every package needed to be recompiled which depends on python)
- the network scripts (rc.inet1) got support for setting up betwork bridges – something I use every day because it allows me to make my Virtual Machines accessible from other computers in my LAN.
- lots of other individual updates (the complete ChangeLog.txt entry of “Mon Jun 25 05:17:48 UTC 2012” measures more than 300 lines)
And since glibc was rebuilt and gcc updated, I needed to create multilib versions of those.
They can be found here (all of the mirrors below also offer rsync access):
- http://slackware.com/~alien/multilib/current/ (master site)
The update to attica-0.4.0 in slackware-current broke many packages of my KDE 4.9-beta2 set. Head over to my other blog post to find out how to fix that easily!
Have fun! Eric