[SOLVED] ImportError: No module named setuptools not on slacbuilds either

BW-userx · 12-22-2018, 07:38 AM

Quote:

Originally Posted by dugan

It does.

No other person on the entire planet has ever had the problem you're apparently posting about.

I'm serious.

It's empty? Good.

Now, what commands are you actually entering that are crashing?

They're clearly very wrong, because your crash messages don't look familiar to me at all, and I have no idea what you did to get them. You want to get this fixed? Post an answer. You want to stay frustrated and ensure it doesn't get fixed? Well, then you can answer it with DO I LOOK LIKE I KNOW PYTHON? again. Your choice.

(Also: you cropped too much of the crash messages to determine anything at all, and the best information we can really give you at this point is "it works for everyone else").

Uh, that's bad.

Have you tried rebooting? (Seriously answer, in case you just messed up something that would be automatically reset with a reboot).

this is sbotools taking care of the deps and what nots, and I did do the Window fix move and that didn't work,

Code:


PRGNAM=glances
VERSION=${VERSION:-2.9.1}
BUILD=${BUILD:-1}
TAG=${TAG:-_SBo}

if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) ARCH=i586 ;;
    arm*) ARCH=arm ;;
       *) ARCH=$( uname -m ) ;;
  esac
fi

CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
PKG=${PKG:-$TMP/package-$PRGNAM}
OUTPUT=${OUTPUT:-/tmp}

set -e

rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
cd $TMP
rm -rf $PRGNAM-$VERSION
tar xvzf $CWD/$PRGNAM-$VERSION.tar.gz
cd $PRGNAM-$VERSION
chown -R root:root .
find -L . \
 \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \
  -o -perm 511 \) -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
  -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

python setup.py install --root=$PKG

find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" \
  | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true

PRGETC=$PKG/etc
PRGUSR=$PKG/usr
PRGSHR=$PKG/usr/share
PRGDOC=$PKG/usr/doc/$PRGNAM-$VERSION

# Move and compress man page.
mv $PRGSHR/man $PRGUSR/
gzip -9 $PRGUSR/man/man1/$PRGNAM.1

# Safely install configuration file.
mkdir $PRGETC
mv $PRGSHR/doc/$PRGNAM/$PRGNAM.conf $PRGETC/$PRGNAM.conf.new

# Install documentation.
mkdir -p $PRGDOC
mv $PRGSHR/doc/$PRGNAM/* $PRGDOC/
cat $CWD/$PRGNAM.SlackBuild > $PRGDOC/$PRGNAM.SlackBuild
rm -rf $PRGSHR

mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
cat $CWD/doinst.sh > $PKG/install/doinst.sh

cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}

BW-userx · 12-22-2018, 07:42 AM

Quote:

Originally Posted by glorsplitz

probably this, works for me on stable, not tried it on current

this only requirement I see on that page is
'This requires: psutil'
https://slackbuilds.org/repository/1...search=glances

Code:

$ sudo sboinstall psutil
psutil (psutil-5.4.8-x86_64-1_SBo) is already installed.

Code:

$ ls /var/log/packages/psutil*
/var/log/packages/psutil-5.4.8-x86_64-1_SBo

sbo link location

https://github.com/nicolargo/glances...s-2.9.1.tar.gz

from the page you gave me

https://nicolargo.github.io/glances/

Code:

$  pip install glances
Traceback (most recent call last):
  File "/usr/bin/pip", line 6, in <module>
    from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

----------
$ sudo pip install glances
Traceback (most recent call last):
  File "/usr/bin/pip", line 6, in <module>
    from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

Now I am running update on slack --current again..

BW-userx · 12-22-2018, 01:16 PM

thanks to another thread for xterm I got ahold of a iso current that ABob makes, used ark untarted it, then went in the parent directory and ran this in the terminal,

Code:

$ while read f ; do  ext=${f##*.} ; if [[ "$ext" = "txz" ]] ; sudo installpkg "$f" ; fi 
done <<<"$(find $(pwd) -type f )"

then I tried installing again, and it worked.

montagdude · 12-22-2018, 02:06 PM

Well I hope you didn't end up with duplicate packages by doing that. Next time you should use upgradepkg --reinstall --install-new instead of installpkg.

BW-userx · 12-22-2018, 02:24 PM

Quote:

Originally Posted by montagdude

Well I hope you didn't end up with duplicate packages by doing that. Next time you should use upgradepkg --reinstall --install-new instead of installpkg.

yeahh I was trying to find that command line googling, but I didn't so remember once i ran something like that and if it was already installed it skipped it, but that could have been third party. I created a boot install stick just in case then I rebooted and it is still running, sooo...

though should it not just install over top of them? current iso just a few days old.

montagdude · 12-22-2018, 02:52 PM

Quote:

Originally Posted by BW-userx

yeahh I was trying to find that command line googling, but I didn't so remember once i ran something like that and if it was already installed it skipped it, but that could have been third party. I created a boot install stick just in case then I rebooted and it is still running, sooo...

though should it not just install over top of them? current iso just a few days old.

The issue would be if you already had some of the same packages installed, but a different version. In that case you would probably just have to removepkg both of them and then install the proper one. I believe that if you do slackpkg update, it will notify you of any such conflicts.

BW-userx · 12-22-2018, 03:00 PM

Quote:

Originally Posted by montagdude

The issue would be if you already had some of the same packages installed, but a different version. In that case you would probably just have to removepkg both of them and then install the proper one. I believe that if you do slackpkg update, it will notify you of any such conflicts.

yeah I ran that already, and just looked in /var/log/packages, and I didn't see anything dupicated

http://bear.alienbase.nl/mirrors/sla...4-current-iso/
updated Sat Dec 22 04:38:27 UTC 2018
so chances are their isn't any conflits in versions.

glorsplitz · 12-22-2018, 05:03 PM

In current, without SBo psutil, SBo glances failed,

Quote:

The 'psutil>=2.0.0' distribution was not found and is required by Glances

I installed SBo psutil, reinstalled SBo glances, glances then worked.

BW-userx · 12-22-2018, 05:11 PM

Quote:

Originally Posted by glorsplitz

In current, without SBo psutil, SBo glances failed,

I installed SBo psutil, reinstalled SBo glances, glances then worked.

Yeah, slackbuilds is

Code:

 $ ls /var/log/packages/psutil*
/var/log/packages/psutil-5.4.8-x86_64-1_SBo

https://slackbuilds.org/repository/14.2/python/psutil/

is was something to do with python on my end, installing packages off the current iso made by ABob fixed it.