Hello people,

I am currently in the process of upgrading and customizing my Slack. I
downloaded slapt-get, but after install, it told me it can't execute
/usr/<something>/slapt-get, so i tried swaret. It performed update and
upgrade (to "current"), downloading about 800 MB. After that, it
started dependency checking. I was shocked when it found hundreds of
missing libraries, that were nowhere to be found. After updatedb and
reboot, the system is quite crippled. It states that openssl is built
against a different version that I have now. Moreover, the X can't be
started, complaining about fonts, about libcairo and several other
things. I guess it all has something to do with swaret. Is it a way to
resolve it?? TIA for any advice.

Mahy

On Sat, 13 May 2006 10:33:03 -0700, Mahy wrote:

> I am currently in the process of upgrading and customizing my Slack. I
> downloaded slapt-get, but after install, it told me it can't execute
> /usr/<something>/slapt-get, so i tried swaret. It performed update and
> upgrade (to "current"), downloading about 800 MB. After that, it
> started dependency checking. I was shocked when it found hundreds of
> missing libraries, that were nowhere to be found. After updatedb and
> reboot, the system is quite crippled. It states that openssl is built
> against a different version that I have now. Moreover, the X can't be
> started, complaining about fonts, about libcairo and several other
> things. I guess it all has something to do with swaret. Is it a way to
> resolve it?? TIA for any advice.

LOL! Yeah, reinstall and forget about using those crappy "managers". As
often as not, your experience above is what happens. Use the built-into
Slackware package management, and avoid those third-party nightmares.

--
If you're not on the edge, you're taking up too much space.
Linux Registered User #327951

Mahy wrote:
> Hello people,
>
> I am currently in the process of upgrading and customizing my Slack. I
> downloaded slapt-get, but after install, it told me it can't execute
> /usr/<something>/slapt-get, so i tried swaret. It performed update and
<SNIP>

Since you didn't mention it, just a reminder that all package managers
must be run as root.

I use slapt-get and gslapt on my machines with no problems. It sounds
like the /usr/sbin/slapt-get may not be set as executable (# chmod 744
/usr/sbin/slapt-get).

On 2006-05-13, Mahy <jkotuc@gmail.com> wrote:
>
> I am currently in the process of upgrading and customizing my Slack. I
> downloaded slapt-get, but after install, it told me it can't execute
> /usr/<something>/slapt-get, so i tried swaret. It performed update and
> upgrade (to "current"), downloading about 800 MB. After that, it
> started dependency checking. I was shocked when it found hundreds of
> missing libraries, that were nowhere to be found. After updatedb and
> reboot, the system is quite crippled. It states that openssl is built
> against a different version that I have now. Moreover, the X can't be
> started, complaining about fonts, about libcairo and several other
> things. I guess it all has something to do with swaret. Is it a way to
> resolve it?? TIA for any advice.


It's certainly possible to get your system back working properly, but
it's not something I'm willing to walk through here. It will involve
booting the Slackware installation cd (or perhaps the Slax livecd),
mounting your / partition (and other system partitions if applicable),
and using some combination of installpkg -root /somedir and/or tar -xzf
to make the system somewhat usable again. I'm guessing that you tried
to upgrade glibc in a multiuser runlevel, and that's one of your problems;
also, there have been quite a few *new* packages added to -current that
would not have been installed with an "upgrade."

I really wish people would realize that there is a very good reason why
Pat doesn't include slapt-get, swaret, et al in the base Slackware
installation (if anywhere at all): using those tools without understanding
how they work is a recipe for disaster. I have personal experience with
slapt-get, so I know that it can be a very *good* tool, but then, I also
understand how it works and I know its limitations.

As a general rule, a distribution update (10.1 --> 10.2 or 10.2 --> 11.0,
but this includes 10.2 --> -current) should never be done with an
automated tool. There will usually be a glibc and/or kernel upgrade, and
almost always new packages that need to be installed for some of the
existing ones' upgraded versions to work properly (see openldap-client
and samba in the -current cycle now). Automated tools will not (and
should not) just automatically install packages that are not already
installed on the system, and this is most likely why you saw so many
missing libraries. Along those same lines, packages are often removed
from the system during a release cycle (for example, see abiword during
this cycle), and although it won't affect whether your systems runs
correctly, housekeeping issues should be enough reason for you to want
those removed.

Finally, the last word on upgrading a Slackware system should logically
come from Pat himself, so here it is:
http://slackware.osuosl.org/slackwar...nt/UPGRADE.TXT

RW

--

http://rlworkman.net

Wow, you've all been quite helpful. Thanks for the Pat's howto on
upgrading. Yes I ran everything as root. I didn't try chmod on
slapt-get executable, i was too perplexed when I found out it doesn't
work. Ok, i'll try to function without these tools. One more thing: the
package libcairo is really nowhere to be found on a mirror! Or am i
wrong again? How else do i get libcairo.so.2?

Mahy

<SNIP>
> work. Ok, i'll try to function without these tools. One more thing: the
> package libcairo is really nowhere to be found on a mirror! Or am i
> wrong again? How else do i get libcairo.so.2?
>
> Mahy

libcairo is part of the cairo package.

If you do decide to use slapt-get, make sure you point to the >stable<
package repositories, not the >current< package repositories.

Once you get slapt-get running (with the appropriate configuration for
where packages are located), you can install the cairo package.

The package I currently have installed is cairo-1.0.2-i486-1frg (the
1frg indicates I installed the package from the FreeRock Gnome
repository).

Well, there's another question: How to (easily) upgrade to "current"
without any 3rd party util while minimizing the risk of landing with
bricked system? Thanks for advice.

Mahy

On Sat, 13 May 2006 10:33:03 -0700, Mahy wrote:

> Hello people,
>
> I am currently in the process of upgrading and customizing my Slack. I
> downloaded slapt-get, but after install, it told me it can't execute
> /usr/<something>/slapt-get, so i tried swaret. It performed update and
> upgrade (to "current"), downloading about 800 MB. After that, it
> started dependency checking. I was shocked when it found hundreds of
> missing libraries, that were nowhere to be found. After updatedb and
> reboot, the system is quite crippled. It states that openssl is built
> against a different version that I have now. Moreover, the X can't be
> started, complaining about fonts, about libcairo and several other
> things. I guess it all has something to do with swaret. Is it a way to
> resolve it?? TIA for any advice.
>
> Mahy
>
Swaret is not part of official slackware. There are a lot of threads
about its deficiencies, and how it can do harm to your system. The best
package management for slackware, especially for someone just starting
out, is just to learn how to do it manually and learn to use the package
manager. One way is to build your own copy of the slackware version you
intend to run. For you, that sounds like slackware-current.

I wrote this to someone else recently who was having trouble with swaret.
Cut and paste here.

Advice: in the future, do yourself a favor and learn how to do it
manually. Follow the instructions in the file (reference above) by
installing the critical packages first, then if you have a slackware
repository you can proceed by running a sequence like this:

for p in a ap d l n x xap;do
for i in $(find $p/. -type f | grep tgz$);do
echo Package: $i
upgradepkg --dry-run $i
done
done

If you pipe the output to a file, you can do more tweaking with individual
packages. You can remove packages don't want at all, or to make sure
packages are added, etc. By reviewing this output in advance you can
avoid some unexpected unpleasant surprises.

--
Douglas Mayne

In article <1147549556.344833.304680@u72g2000cwu.googlegroups .com>,
"Mahy" <jkotuc@gmail.com> wrote:

> How else do i get libcairo.so.2?

You can search for filenames within stock Slackware packages using the
package browser: http://www.slackware.it/en/pb/

"Mahy" <jkotuc@gmail.com> writes:

> Well, there's another question: How to (easily) upgrade to "current"
> without any 3rd party util while minimizing the risk of landing with
> bricked system? Thanks for advice.

current is the development version, the pre release version. 10.2 is the
latest release at this time.

***Next is how I keep Slackware-current up to date*** it's NOT how to upgrade**
perhaps my home brewed method anyways until I improve upon it. it works for me

(I start off with current as in why upgrade when I don't have to)a few ISO's of
current used to exist on the web but then I learned how to make my own ISO's.

http://uselesstree.org/live/tree/gro...mplete_Slacker

I've benefited from some of the info there. I don't use all of it -- for
instance I have my own Perl script that checks the changelog -- but I need to
write/program some more bells and whistles into it so it will auto update
itself once it has reported to me that package updates are available. Since I
don't manually edit/update it, I then took to merely using a bookmark in my web
browser to check via http the changelog once in a while.

I've an 80 GB USB external HD that stores my mirror. I just sync it via ftp
or rsync with a web mirror (of current) once in a while.

discretion needed on the next method. It works very fine but I've not been
doing it for very long (I'm sure some packages could not update via the next).

From changelog, I copy and paste into an editor such things as:

ap/cdrdao-1.2.1-i486-1.tgz: Upgraded to cdrdao-1.2.1.
ap/mysql-5.0.21-i486-1.tgz: Upgraded to mysql-5.0.21.

my editor can do regex replace to rid of unneeded so that I result in only
the paths and filenames, thus:

ap/cdrdao-1.2.1-i486-1.tgz
ap/mysql-5.0.21-i486-1.tgz

I save that as text file with date, thus:

slak_cur_upd051306.txt

Then as root I cd into the slackware directory of my local mirror.

Then (since I so far learned more of Perl than I learned of shell script) I
run a Perl script that reads my text file into an array and then hands off
to upgradepkg doing so one package at a time until the mentioned upgrade
list is exhausted.

You can tell that I use the script for more than just multiple
(and selective) upgradepkg

from slackware dir. of my local mirror, the command:

# perl_script slak_cur_upd051306.txt

#!/usr/bin/perl -w
use strict;

# http://download.kde.org/download.php
# my $base = 'ftp://ftp.oregonstate.edu/pub/kde/stable/3.5.2/contrib/Slackware/10.2/';
# my $base = 'ftp://mirrors.kernel.org/fedora/core/5/i386/iso/';
my $old = shift;
open(OLD, "<", $old) or die "cant open $old: $!";
my @lines = <OLD> ;
close(OLD) or die "cant close $old: $!";

foreach my $line ( @lines ) {
chomp($line);
# system("wget $base$line");
# system("wget $line");
# system("md5sum $line");
# system("identify $line");
system("upgradepkg $line");
} # end

--
abc Alan_Cu b c n u