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.
As mentioned here xf86-video-modesetting is deprecated and already included in xorg-server 1.17.x: The package of xf86-video-modesetting includes the same drivers/files as included in the xorg-server package.
The package xorg-cf-files has "noarch" in the name while it installs files into lib64 and the files are different to the 32bit package, at least /usr/lib[64]/X11/config/X11.tmpl
BlueZ 5.x dropped support for Alsa: http://git.kernel.org/cgit/bluetooth...328cb0b1ab0818
Are we getting PulseAudio as well?
Without it, a2dp-sink is pretty much dead, and to make it worse, errors are quite non-descriptive
This is bad. I knew blueman didn't support bluetooth audio except via PA, but I was not aware that alsa support had been completely dropped from bluez5. :/
I'll talk with you on IRC about this more...
Maybe other scripts are worth considering, but those listed above were easier to spot as their internationalized counterparts already use the --visit-items option.
Last edited by Didier Spaier; 12-28-2015 at 05:24 AM.
Reason: s/--list-items/--visit-items/
I was trying to check the issue described in this thread and found something i maybe doing wrong:
I was going through the setup until i get asked to select the Prompting Mode. I choose "custom". From the help:
Quote:
If at any point a tagfile with that extension cannot be found, the default tagfile will be used instead.
So i assume that if i want to use a custom tagfile for only one category, i do only add a file named like tagfile.tst and for all the other categories setup will use the default tagfile without any extension, right? I added .tst as custom extension for tagfiles and continued.
Well, maybe i'm doing something wrong, but all i get is a massive list of errors, see screenshot. Nothing will be installed.
From the slackinstall file:
Code:
cp -a $SRCPATH/$series/tagfile`cat $TMP/SeTtagext` $TMP/tagfiles/$series/tagfile
I don't see any code that will search for the default tagfile if tagfile.tst does not exist and thus slackinstall will fail to install. Either this should be fixed or the helptext should be fixed
Last edited by DarkVision; 01-13-2016 at 12:49 AM.
The SlackBuild script for Tcl should be checked. It will compress all manpages by default while a lot of the manpages will be installed as man.x.gz already. On -current this will result in a large list of broken symlinks. Example:
Code:
./usr/man/man3/Tcl_GetAliasObj.3.gz.gz: broken symbolic link to Tcl_IsSafe.3.gz.gz
The file that will be installed is Tcl_IsSafe.3.gz and the SalckBuild will try compress this file again. GZip will skip these files since they already have the .gz extension, but the following symlink-check will change the target+name of the symlink by blindly adding .gz again.
This is what makepkg reports for the above file using the original SlackBuild
Code:
Searching for symbolic links:
usr/man/man3/Tcl_GetAliasObj.3.gz.gz -> Tcl_IsSafe.3.gz.gz
This is how the line should look like:
Code:
Searching for symbolic links:
usr/man/man3/Tcl_GetAliasObj.3.gz -> Tcl_IsSafe.3.gz
Here is a quick patch, 1st try:
Code:
--- tcl.SlackBuild.orig 2015-11-11 18:34:37.000000000 +0100
+++ tcl.SlackBuild 2015-12-28 19:44:38.694702876 +0100
@@ -121,8 +121,8 @@
| grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null
# Compress manual pages:
-find $PKG/usr/man -type f -exec gzip -9 {} \;
-for i in $( find $PKG/usr/man -type l ) ; do
+find $PKG/usr/man -type f -name "*.?" -exec gzip -9 {} \;
+for i in $( find $PKG/usr/man -type l -name "*.?" ) ; do
ln -s $( readlink $i ).gz $i.gz
rm $i
done
I'll search for files not ending with .gz since there are still some uncompressed man pages.
I have found some more broken symlinks... attached is a short list. I have to spent some more time to see if this is a result of my lite-install (skipping all optional packages, see this thread) or if more SlackBuilds need to be checked. On a first look the libzip-package has also some bad symlinks (broken symbolic link to /tmp/package-libzip/usr/man/...)
<edit>Updated list with broken symlinks... the old list included only links in /usr</edit>
Last edited by DarkVision; 01-13-2016 at 12:49 AM.
JIC this gets in: for anyone managing existing php sites, here is a summary of the backward incompatible changes with version 7 http://php.net/manual/en/migration70.incompatible.php
what is not cited there is that the mysql extension that a lot of (old) sites still running use, after being deprecated since php-5.5.x, with this release is removed (but it's still available as a PECL extension).
For the above report about <edit>slackinstall</edit> not using the default tagfile if no tagfile with a custom extension is found i'll have created a patch. Right now if you choose custom tagfiles you need to have a custom tagfile for each series. The helptext sayz that if a custom tagfile is missing the default tagfile will be used.
I'm still not sure if i have miss-read the help-text or if this is really an issue. Just ignore this patch if me is wrong
Code:
--- slackinstall.orig 2015-12-24 20:38:24.000000000 +0100
+++ slackinstall 2015-12-28 18:16:21.000000000 +0100
@@ -80,7 +80,11 @@
cp -a `cat $TMP/SeTtagpath`/* $TMP/tagfiles
elif [ $MODE = custom ]; then
mkdir -p $TMP/tagfiles/$series
- cp -a $SRCPATH/$series/tagfile`cat $TMP/SeTtagext` $TMP/tagfiles/$series/tagfile
+ if [ -r $SRCPATH/$series/tagfile`cat $TMP/SeTtagext` ]; then
+ cp -a $SRCPATH/$series/tagfile`cat $TMP/SeTtagext` $TMP/tagfiles/$series/tagfile
+ else
+ cp -a $SRCPATH/$series/tagfile $TMP/tagfiles/$series/tagfile
+ fi
elif [ $MODE = menu -o $MODE = expert ]; then
cat $TMP/series/series.in | while read series ; do
if [ $MODE = menu ]; then
Here is the helptext from setup:
Quote:
To use a custom tagfile, just choose "custom" on the
prompt mode menu, and enter your custom extension. Any
tagfiles with this extension will then be used for the
duration of the installation. If at any point a tagfile
with that extension cannot be found, the default tagfile
will be used instead.
Last edited by DarkVision; 12-28-2015 at 02:27 PM.
Reason: fixed typing errors...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
