Great to see so many interesting updates to the Slackware-current!
I had to update glade3 from the Slackware-current 3.8.5 to 3.18.3 that
now includes 'libgladeui', which is requested (to build) recent versions of anjuta,
gtksourceview3, libgda, libpeas, ...
Besides, I'd add devhelp (an API documentation browser for GTK+ and GNOME),
which is helpful ;-) for various GTK+ programs.

the build scripts for all of these version bumps should be already available on my personal (and unofficial) repository for current.

BTW, small OT: nice photos you got on flickr, igor!

the ChangeLog "Please enjoy "almost a beta."

it smells new version

Thanks, I'll compare it with my SlackBuid.
Grazie, Matteo! :-)

ChangeLog: (Sorry we missed Friday the 13th this time)


For, Pat and all, 13 is disatrous and sinister date here, in France.

Eudev-3.1.5 works good. As a matter of fact, I've been using eudev for some time now without issue.

I haven't had the libudev.so.1 versus libudev.so.0 issue oddly, though in my Slackworks build I did link libudev.so to so.1 and so.0 equally, but nothing hiccupped.

With the standard rc scripts there is a little extra output, but nothing bad. OpenRC from SBo doesn't have any issues either.

1 members found this post helpful.

good news I wanted to ask you if you have tested

Hi,

Maybe it would be a good idea to pull-in:
1. http://slackbuilds.org/repository/14...tel-microcode/
2. http://slackbuilds.org/repository/14...m/iucode_tool/

and teach people in the ANNOUNCE.x or CHANGES_AND_HINTS.TXT on how to apply the microcode early in the boot?

Or isn't the problem with Intel's CPUs so widespread?

--
Best regards,
Andrzej Telszewski

If suggestions are still open, I suggest giving consideration to one further issue, namely whether to package as elilo-x86_64.efi not the pre-compiled binary supplied by the author of lilo, but the one compiled but discarded by elilo.SlackBuild. I realise why this is currently done - because elilo-ia32.efi cannot conveniently be compiled on a 64-bit machine - but the elilo package can provide the author's precompiled elilo-ia32.efi and the slackware compiled elilo-x86_64.efi. This would enable elilo-x86_64.efi to be signed. The pre-compiled one has been compiled by the author against too old a version of gnu-efi to enable it to be signed.

I agree this is of marginal utility given that slackware does not support secure boot out of the box, but providing for secure boot for slackware is relatively trivial for a user, and this would make it just a little easier.

Yeah, and I've been using it for a while now, even before Patrick dropped it in.

I would say, if he wants to rebuild everything using it, go ahead. What exactly was the problem with the new ABI? A few binary only packages?

proftpd 1.3.5a bugfix-release is out since a few months, disabling sslv3 among others.
Please consider adding "mod_sftp". Sftp is covered also by openssh, but with proftpd there would be the advantage of maintaining users in a file/db, instead of being forced to add system-users.

1 members found this post helpful.

Wow, that is the most green I've seen on distrowatch in a long time (it's still a great reference to see how bleeding edge Slackware is, even if the metrics for measuring a distro's popularity based on page hits is questionable). There were two that stood out that look like they'd be problem-free updates (just based on the relatively small version change numbers).

dhcpcd 4.3.2 -> 4.3.3
php 5.6.14 -> 5.6.15

The others, just for reference, are:

bash 4.3 -> 4.3.30
cups 2.0.4 -> 2.1.0
linux 4.1.13 -> 4.3
mariadb 10.0.22 -> 10.1.18
openssl 1.0.1p -> 1.0.2d
Python 2.7.10 -> 3.5.0
qt 4.8.7 -> 5.5.1

Everything else is green

1 members found this post helpful.

I've reported the error in the bash version description to DistroWatch since -current now uses bash 4.3.042 which is the latest version/patch level.

1 members found this post helpful.

That did seem a little strange to me considering all the bash updates we've had over the past year or so, but I didn't bother to do any digging. Thanks for the update!

EDIT: I'll shoot an email to them as well. Maybe multiple squeaks will get the wheel fixed.

Are we ever going to see NFSv4 support? If not, why not? Almost every other distro supports NFSv4 and many distros automount NFS shares as NFSv4 now.

1 members found this post helpful.