[SOLVED] multilib question

jkirchner · 08-20-2014, 07:47 AM

I would like to come back to Slackware

I have a question on the multilib. I have read Alien Bob's directions but I am curious, should I run the process from console or is it okay to run from the graphical desktop? I tried multilib a while back using slackpkg+ and it all ran but I had a small list of errors at the end.

Ultimately what I want to do with the computer is learn programming, scripting etc and also, of course, a little gaming. I will get Alien Bob's Steam package when all is done. Both my laptop and desktop are 64bit OS's now and I assume that is best way to go and add multilib, true?

Slackware was actually the first version of Linux distros I tried (9.0 I believe) and then I have strayed and wandered the Debian/Ubuntu/Mint trail on and off. Nothing runs as snappy and crisp as Slackware so I want to come home

Just need to verify this multilib thing. I want to do it right.

Drakeo · 08-20-2014, 08:33 AM

Hi jkirchner you know I been running multi lib since 13.0. and tell you the truth I wrote a script that handles updating my system and not affecting everything.
this is my way so take a deep breath and sit a while. first I run this script as root to install multi lib.
Name it multi-lib-install.

Code:

#!/bin/sh

##INSTALL NEW MULTI-LIB
mkdir /var/cache/multilib/
mkdir /var/cache/multilib/slackware64-compat32
rsync -r -a -v --bwlimit=300 --delete --progress --stats rsync://rsync.slackware.org.uk/people/alien/multilib/14.1/ /var/cache/multilib/
cd /var/cache/multilib/
upgradepkg --reinstall --install-new *.t?z
cd /var/cache/multilib/slackware64-compat32#installpkg *?/*.t?z


##UPGRADE MULTI-LIB
rsync -r -a -v --bwlimit=300 --delete --progress --stats rsync://rsync.slackware.org.uk/people/alien/multilib/14.1/ /var/cache/multilib/
cd /var/cache/multilib
upgradepkg --install-new *.t?z
cd /var/cache/multilib/slackware64-compat32
upgradepkg --install-new *?/*.t?z

then I edit my /etc/slackpkg/blacklist

Quote:

# This one will blacklist all SBo packages:
[0-9]+_SBo
[0-9]+alien
[0-9]+compat32

then I make have a script I name slack-multi-update. I place it in my /usr/local/bin

Code:

 #!/bin/bash
# Init
FILE="/tmp/out.$$"
GREP="/bin/grep"
#....
# Make sure only root can run our script
if [ "$(id -u)" != "0" ]; then
   echo "This script must be run as root " 1>&2
   exit 1
fi

# ...

slackpkg update

echo -e "\e[1;33m If this was a distro version upgrade 
you may want to edit your /etc/slackpkg/blacklist so any programs
from Slackbuilds may have been added to Slackware. please read
http://slackware.org.uk/slackware/slackware64-current/CHANGES_AND_HINTS.TXT
 so you can remove any unused packages\e[0m"

echo -e "\e[1;31m Going to look for new packages \e[0m"
sleep 10

slackpkg install-new

sleep 3

slackpkg upgrade-all

echo -e "\e[1;33m Going to upgrade multilib \e[0m"
sleep 5

##UPGRADE MULTI-LIB
rsync -r -a -v --bwlimit=100 --delete --progress --stats rsync://rsync.slackware.org.uk/people/alien/multilib/14.1/ /var/cache/multilib/
cd /var/cache/multilib
upgradepkg --install-new *.t?z
cd /var/cache/multilib/slackware64-compat32
upgradepkg --install-new *?/*.t?z

echo -e "\e[1;33m system is up to date \e[0m"
sleep 5



exit

now I go into my kde menu editor and create a new "item" under "system" name it "slack-multi-update".
then point it to the script. then click advanced then select run in terminal, then select run as another user select root.
select your favorite icon and save.
make sure you make the script is executable. The script will only run as root. and when you click on it in the kde menu
it will ask for your root password.
I would suggest sending Alien Bob a donation he works hard and does a great job.
This little script has helped me and a few friends a long time.
I also have that script for current and it works fine.

TobiSGD · 08-20-2014, 08:59 AM

The easiest way nowadays is to just use slackpkg+ to install and maintain multilib, used it for a while, never had any problems.

jkirchner · 08-20-2014, 09:27 AM

Quote:

Originally Posted by TobiSGD

The easiest way nowadays is to just use slackpkg+ to install and maintain multilib, used it for a while, never had any problems.

I can try it again. As I said, I did get errors (packages not installed, cannot recall exactly). Is it better to run slackpkg+ for the multilib from console for the first time or is it okay to run it from KDE and Konsole?

Drakeo, that is neat little script. I see it follows along with most of what AlienBob outlined except he used lftp instead of rsync (I have never used rsync will read up on that).

I was not sure where it was meant to mkdir for this:

Code:

# SLACKVER=14.1
# mkdir multilib
# cd multilib
# lftp -c "open http://taper.alienbase.nl/mirrors/people/alien/multilib/ ; mirror -c -e ${SLACKVER}"
# cd ${SLACKVER}

but /var/cache makes sense.

I know, I know, I get nervous over the little things I guess

If I understood what I read about slackpkg+ it is an add-on to slackpkg, so once I set it up, it would update everything I needed for the system as well as multilib. True?

Getting ready to do the Slackware64 install today

TobiSGD · 08-20-2014, 10:21 AM

Best bet would be to run it from console, but so far I never had problems running it in runlevel 4.

Quote:

If I understood what I read about slackpkg+ it is an add-on to slackpkg, so once I set it up, it would update everything I needed for the system as well as multilib. True?

True. It will install updates for any repo you have configured, I usually added AlienBob's repositories (the normal and the restricted) and multilib, worked fine.

lems · 08-20-2014, 10:24 AM

For what it's worth, here is a post by phenixia2003 outlining how to install multilib on Slackware: http://www.linuxquestions.org/questi...9/#post5066064

jkirchner · 08-20-2014, 11:36 AM

Thanks all, going to install now and say bye to Mint. Back later if I have more questions!

I truly appreciate all the great advice passed on to me.

jkirchner · 08-20-2014, 02:48 PM

Slackware64 installed, ready to go multilib

The first issue I ran into was gpg, I had to run the reinstall with checkgpg=off, which, since it was AlienBob's repo I felt okay with of course.

But, this is where I get "stuck". These are the "errors" I mentioned earlier. What is the best way to fix this?

Code:

=============================================================================
  WARNING! One or more errors occurred while slackpkg was running
------------------------------------------------------------------------------

http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1/slackware64-compat32/x-compat32/libXevie-compat32-1.0.3-x86_64-1compat32.txz:    download error
libXevie-compat32-1.0.3-x86_64-1compat32.txz:   md5sum

http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1/slackware64-compat32/x-compat32/libXmu-compat32-1.1.2-x86_64-1compat32.txz:      download error
libXmu-compat32-1.1.2-x86_64-1compat32.txz:     md5sum

http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1/slackware64-compat32/x-compat32/libXrender-compat32-0.9.8-x86_64-1compat32.txz:  download error
libXrender-compat32-0.9.8-x86_64-1compat32.txz: md5sum

http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1/slackware64-compat32/l-compat32/libffi-compat32-3.0.13-x86_64-2compat32.txz:     download error
libffi-compat32-3.0.13-x86_64-2compat32.txz:    md5sum

http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1/slackware64-compat32/x-compat32/libfontenc-compat32-1.1.2-x86_64-1compat32.txz:  download error
libfontenc-compat32-1.1.2-x86_64-1compat32.txz: md5sum

http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1/slackware64-compat32/n-compat32/p11-kit-compat32-0.16.4-x86_64-1compat32.txz:    download error
p11-kit-compat32-0.16.4-x86_64-1compat32.txz:   md5sum

http://taper.alienbase.nl/mirrors/people/alien/multilib/14.1/slackware64-compat32/n-compat32/p11-kit-compat32-0.16.4-x86_64-1compat32.txz:    download error
p11-kit-compat32-0.16.4-x86_64-1compat32.txz:   md5sum

[edit]Here is what I think will fix it and what I am trying. I see the files are in the slackware_64-compat32 directory so I am d/l them from Alien's site now and can install from there. I think that will do the trick.

garpu · 08-20-2014, 03:52 PM

I think when I installed the multilib stuff I was in X. I don't think it matters.

Note that if you're using nvidia's drivers that you'll have to reinstall them once you reboot. (Be sure to install the 32-bit utilities, as well. The driver installer will prompt you. Disregard if you don't have an nvidia card or update your drivers on some other fashion.)

jkirchner · 08-20-2014, 04:19 PM

Quote:

Originally Posted by garpu

I think when I installed the multilib stuff I was in X. I don't think it matters.

Note that if you're using nvidia's drivers that you'll have to reinstall them once you reboot. (Be sure to install the 32-bit utilities, as well. The driver installer will prompt you. Disregard if you don't have an nvidia card or update your drivers on some other fashion.)

Got it. Yes, I found out about the nvidia drivers. I did the multilib and then got Steam from Alien's site and it segfaulted, googled that and found the Nvidia tip. Just reinstalled that and bang Steam is up and going Multi-Lib is up...woot

Now to kill Mint on my laptop....

Thanks to all that assisted!!!!

Drakeo · 08-20-2014, 04:48 PM

Quote:

Originally Posted by TobiSGD

The easiest way nowadays is to just use slackpkg+ to install and maintain multilib, used it for a while, never had any problems.

I agree that may be the best for you and it works well for one repo rebuild of slackware but my thoughts follow on slackpkg+

Tobi that's not true I want you to have a system already installed with many programs you have built custom for your computer and for proprietary stuff. I love what Eric is doing but trust me I spent a couple months setting up a system with all slackpkg+ and it does not come near what I need for my system.

I think it is a great step to try to make every one have the same duck in the same row. But it breaks most of the stuff I need at times during updates How long is my blacklist going to be. Now that said if I was just going to live blind and be spoon fed what ever program some guy throws at me. then I would never use Slackware. Heck I use Ubuntu systemd.
The alien bob repo is impressive and I do look at some of his build scripts. He does take time to show dependencies.

But is it really the best way?

People come to Slackware for many reasons. and some will love just configuring your alien bobs source repos.
I gave it a honest try. But Like I said it is not my duck and not my row.
"To say that is the best way" makes me wonder if that's all you have is a generic cpu.

There is more than one way to build these programs and get more out of your system.
Hey if you think reliability is one mans repo or another mate msb etc etc. Then ask Pat why he always has the source code with his builds. because we need to do things a certain way.
when alien bobs repo and sources did not always match Slackbuilds it is a build it with scripts to build each program with the dependencies so you can edit the
scripts during a build like Mate or KDE or etc etc or Even Eric H ffmpeg build script. . then we are talking. You have any Idea how many ways there is to put ffmpeg together. And if it is not built right it will break other things. If you build it with celt and celt is updated
you can run in to a huge Schrodinger.

I will agree for people that want the simple install me fine. I got my Slackback a long time ago.
learning builds knowledge That brings forth better feed back.

Would I point some one to use slackpkg+ sure only after they learned Slackware. There is nothing more frustrating then some program broken during an update.

jkirchner · 08-20-2014, 05:12 PM

@Drakeo. I am going to give your script the try on the laptop I am doing next. I have read through it a few times and see what it is doing. I am enjoying learning different things with this process.

55020 · 08-20-2014, 06:28 PM

@Drakeo - yes slackpkg+ really is the best way of installing and upgrading packages from multiple package repositories, but it is not the whole picture. slackpkg+ does one job and does it well. But the tool that does what you want to do is slackrepo, which is intended to bridge the gap between git repos of slackbuilds (yours, or SBo, or csb, or msb, or upversioned slackbuilds from Slackware's source tree) and slackpkg+. slackrepo will track git updates and build them cleanly into properly maintained repositories for your lan or the whole internet. Of course you are welcome to do that job manually if you prefer... but it is really nothing to do with slackpkg+.

Drakeo · 08-21-2014, 03:48 AM

Quote:

Originally Posted by 55020

@Drakeo - yes slackpkg+ really is the best way of installing and upgrading packages from multiple package repositories, but it is not the whole picture. slackpkg+ does one job and does it well. But the tool that does what you want to do is slackrepo, which is intended to bridge the gap between git repos of slackbuilds (yours, or SBo, or csb, or msb, or upversioned slackbuilds from Slackware's source tree) and slackpkg+. slackrepo will track git updates and build them cleanly into properly maintained repositories for your lan or the whole internet. Of course you are welcome to do that job manually if you prefer... but it is really nothing to do with slackpkg+.

I agree to disagree I understand where it comes from. it is all rysnc. And when Patrick encludes it. All of it in slackware that is fine.
then we will have an option to install or not from disk. It is not official all the repo's. There is only two official lines of slackware.
one is x86 the other x86_64. the rest is out side the official release. If you think you can maintain a multi-lib system with just slackpkg+ then you have not
taken the time to compile and run everything from a x86_64 machine. I mean do not boot a x86 machine to build your compat.

Now build it all from the x86_64 and you will begin to see the problems that will occur. I love what Eric is doing I support his effort.
I just do not advise people to use something I know has a long way to go before I can recommend something only tested.

This has a lot to do in how the developers set the software up to build.
The best way I guess would have a script on git that handles it from source the way dependencies are built for 32compat from a x86_64 machine. Never as simple as
slackpkg+ upgrade-all. I really wish it was.

slackpkg is one of them programs in slackware if not used as a correct tool may create a serious problem.
this thread is about "multilib question"

Drakeo · 08-21-2014, 05:42 AM

reply to 55020

Quote:

But the tool that does what you want to do is slackrepo,

I forked that git repo and have begun looking at it. Wow this is very impressive and can lead to some very exciting repositories in the future.
This is great concept and looking at the functions for multi-lib it really has a good start no doubt this could be the way of the future for.
custom repos and an exciting way for better enterprise abilities for Slackware.