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.
sysinit-2.89 was never released and possibly never will be. A thread about that was opened on Sat, 08 Feb 2014 by Petter Reinholdtsen but leaded to no decision AFAIK.
Furthermore Slackware just ships the directory structure and the functions script that PV took from Fedora and that does its job of coping with software that expect to find "Red Hat-isms".
So I fail to see how this could trigger a desired update to -current. Unless there be a need to update that script, of course. Is there one?
Maybe one could request instead something to help software find the new "Fedora-isms" they are looking for but we have had already too many threads on that topic
Last edited by Didier Spaier; 07-09-2015 at 04:27 PM.
True Didier and sysvinit more or less is only used as a utility for startup, shutdown, and reboot for most systems that don't use the classic init style scripting like Slackware. Still interesting to see an update, forked or unofficial.
Also how does openssl-1.0.1 series compare to 1.0.2? I think only one package, wget, had some problems with it, so a few distros using it went with gnutls.
This isn't a desired update, but rather a missing dependency for mytop (part of mariadb). When running mytop I get this error.
Code:
bash-4.2$ mytop
Can't locate Term/ReadKey.pm in @INC (you may need to install the Term::ReadKey module) (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /usr/bin/mytop line 192.
mytop requires perl-TermReadKey from SBo. This is an issue on both Slackware 14.1 as well as Slackware -current. Once perl-TermReadKey is installed then mytop works.
Code:
bash-4.2$ mytop
Cannot connect to MySQL server. Please check the:
* database you specified "test" (default is "test")
* username you specified "root" (default is "root")
* password you specified "" (default is "")
* hostname you specified "localhost" (default is "localhost")
* port you specified "3306" (default is 3306)
* socket you specified "" (default is "")
The options my be specified on the command-line or in a ~/.mytop
config file. See the manual (perldoc mytop) for details.
Here's the exact error from DBI. It might help you debug:
Can't connect to local MySQL server through socket '/var/run/mysql/mysql.sock' (2)
I didn't have mysql started when I ran this so the socket error is expected.
I'd like to see this patch to cdparanoia included, personally. Don't see much reason not to include a patch that fixes a show-stopping bug. Especially for cdparanoia, whose last official release was, what, 2008?
This probably won't bother most Slackware users but here's a quick report on a casualty of removing gnome-icon-theme: Ekiga-4.0.1 seems to require it at compile-time:
Code:
checking for intltool >= 0.35.0... 0.50.2 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.18.1
checking for XML::Parser... ok
checking for GTK... no
configure: error: Package requirements (gtk+-2.0 >= 2.20.0 gnome-icon-theme >= 3.0.0) were not met:
No package 'gnome-icon-theme' found
It seems that 5.0 will be gtk+3-based so I doubt this requirement will go away. I recall that removing gnome-icon-theme broke the icons in pavucontrol (this is relevant to others who have also integrated PA into their Slackware installations). So this run-time dependency may also apply to more general-use apps like gnome-disks etc.
No real need for a gnome-icon-theme package for Slackware-14.2, every case I have found so far can simply have adwaita-icon-theme substituted, the patch is almost always trivial, just fixup configure.in and do whatever autoreconf hand-waving that may be required.
I am on stable, not on -current, but for what it's worth I see video regressions with kernel 3.18.11.x64 compared to 3.10.59.x64. My VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) turns backlight on and off semi-randomly, and sometimes the Fn brightness keys stop working.
I am on stable, not on -current, but for what it's worth I see video regressions with kernel 3.18.11.x64 compared to 3.10.59.x64. My VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) turns backlight on and off semi-randomly, and sometimes the Fn brightness keys stop working.
My Lenovo T41 laptop running intel graphics on Slackware64-current fails to load x windows and XFCE 4.12 from run level 3 on a regular basis. That is, issuing the startx command often fails and drops back to a cursor prompt. It will load x windows on the next attempt.
Hi Eric Hameleers - I'm hoping that, as a previous contributor to the samba SlackBuild, you could shepherd through a potential fix I'm suggesting below for a problem I found with the samba package in -current.
The problem first became apparent after running 'pkg-config --libs samba-util' which resulted in error msg about missing tevent. Actually, tevent libs are supplied in the samba package however there is no tevent.pc for pkg-config to know about them. Furthermore there is no tevent.h supplied at all. Looking through the samba.SlackBuild, I see that similar problems with talloc, pytalloc and tdb are currently being dealt with by manual copying of respective .pc & .h files from the build tree into the $PKG tree (as well as adding some symlinks for the shared objects). BTW the copied .h files are currently copied into $PKG/usr/include instead of $PKG/usr/include/samba-$VERSION (where all other samba .h files are installed).
All these problems can be fixed without the manual copying i.e. have them installed correctly by samba's own build system, by adjusting the wscript files for the tevent, talloc & tdb projects in the samba source tarball. I've attached a patch that makes these adjustments so that 'make install DESTDIR=$PKG' will do the right thing i.e. it includes the .pc & .h files in the package directory. A second patch is attached for samba.SlackBuild itself - to include the first patch and remove the now extraneous manual copying of the various files involved.
I suggest that doclifter from Eric S. Raymond be added to the linuxdoc-tools package.
This would complement this package with two handy Python scripts and associated man pages (also in html format):
doclifter translates documents written in troff macros like man pages to DocBook, that can then be converted to other formats or translated, using the other tools shipped in linuxdoc-tools.
manlifter is a mass-conversion script and test harness for doclifter. It can find and convert _all_ man pages in your system with one simple command, but in a few cases where it fails (mostly because of formatting errors in the man page that it can also help find).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.