shaman doesn't show...

jumbotron · 2010-02-10 23:42:45

hi there...

1-installed SHAMAN but doesn' show(from menu lxde) i no shaman is buggy but how can start it?

2-

# pacman -Syu
:: Synchronizing package databases...
 testing is up to date
 core is up to date
 extra is up to date
 community is up to date
:: Starting full system upgrade...
:: Replace klibc with testing/mkinitcpio? [Y/n]

how to act? yep or nope?

Last edited by jumbotron (2010-02-10 23:43:36)

tomk · 2010-02-11 00:22:58

2. If you're using testing, you should be reading the arch-dev-public ML, where you will find the answer to this question (it's Y, btw). More generally, use some common sense - do you think pacman would offer you a replace option if the devs didn't want a package replaced? These things don't happen by accident, you know.

jumbotron · 2010-02-11 01:18:28

hi!

1-got this message from terminal: it is possible to fix it?

$ shaman
shaman: error while loading shared libraries: libpolkit-qt-core.so.0: cannot open shared object file: No such file or directory

# shaman
shaman: error while loading shared libraries: libpolkit-qt-core.so.0: cannot open shared object file: No such file or directory

btw...i'm newbie to arch...

Last edited by jumbotron (2010-02-11 01:19:09)

jowilkin · 2010-02-11 01:39:53

I think that error is due to shaman being built against an older version of polkit-qt package. You could probably build shaman from ABS source to solve it, but I can't guarantee it will work.

Edit: I tested the pkgbuild in ABS and it's pretty broken unfortunately.

Last edited by jowilkin (2010-02-11 01:44:47)

tomk · 2010-02-11 15:25:54

If you're new to Arch, I strongly recommend that you stop using the testing repo.

And just so you're aware, shaman is an unofficial pacman frontend - try here for support.

Allan · 2010-02-11 15:55:55

jowilkin wrote:

Edit: I tested the pkgbuild in ABS and it's pretty broken unfortunately.

You probably needed to rebuild aqpm first.

foggybrain · 2010-02-11 19:49:50

shaman is defo knackered

tried rebuilding from the PKGBUILD (Community) but cmake can find polkit bits.

Aqpm Found
-- Found LibArchive: /usr/lib/libarchive.so
-- Found Automoc4: /usr/bin/automoc4
-- checking for module 'polkit>=0.8'
-- found polkit, version 0.9
-- checking for module 'polkit-dbus>=0.8'
-- found polkit-dbus, version 0.9
Plasma not found, plasma components won't be built
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
POLKITQT_CORE_LIBRARY
linked by target "shaman" in directory /home/tim/aur/builds/shaman/src/drf-shaman1-a47d6e0/src
POLKITQT_GUI_LIBRARY
linked by target "shaman" in directory /home/tim/aur/builds/shaman/src/drf-shaman1-a47d6e0/src

-- Configuring incomplete, errors occurred!
==> ERROR: Build Failed.
Aborting...

so I tried rebuilding aqpm

==> Starting build()...
-- Found Qt-Version 4.6.1 (using /usr/bin/qmake)
-- Found Threads: TRUE
-- Found Automoc4: /usr/bin/automoc4
-- Found Alpm: /usr/lib/libalpm.so
-- WARNING: you are using the obsolete 'PKGCONFIG' macro use FindPkgConfig
-- PKGCONFIG() indicates that polkit-qt-core is not installed (install the package which contains polkit-qt-core.pc if you want to support this feature)
-- Cannot find Polkit-Qt library!
CMake Error at libaqpm/worker/CMakeLists.txt:35 (dbus_add_activation_system_service):
Unknown CMake command "dbus_add_activation_system_service".

-- Configuring incomplete, errors occurred!
make: *** No targets specified and no makefile found. Stop.
==> ERROR: Build Failed.
Aborting...

jowilkin · 2010-02-11 19:57:11

Allan wrote:

jowilkin wrote:
Edit: I tested the pkgbuild in ABS and it's pretty broken unfortunately.
You probably needed to rebuild aqpm first.

I can't get aqpm to build either. There are problems with the md5sums in shaman and aqpm PKGBUILDS. Then there are problems with _sha1id variables in each PKGBUILD. If I fix both those problems, both packages will make it to the configure stage and fail there.

Edit: foggy beat me to it, I get same errors as him (after applying the fixes mentioned above).

Last edited by jowilkin (2010-02-11 19:58:03)

jumbotron · 2010-02-12 15:23:59

hi fellows...this one is the last i bother{i hope so:lol:] btw i stop use [testing] repo:

# pacman -Su
:: Starting full system upgrade...
warning: cryptsetup: local (1.1.0-2) is newer than core (1.1.0-1)
warning: device-mapper: local (2.02.60-3) is newer than core (2.02.60-2)
warning: filesystem: local (2010.02-1) is newer than core (2010.01-1)
warning: lvm2: local (2.02.60-3) is newer than core (2.02.60-2)
warning: mkinitcpio: local (0.5.99.5-1) is newer than core (0.5.30-1)
warning: rp-pppoe: local (3.10-3) is newer than core (3.10-2)
warning: tcp_wrappers: local (7.6-11) is newer than core (7.6-10)
 local database is up to date

how can i handle it?

Last edited by jumbotron (2010-02-12 15:25:36)

toad · 2010-02-12 15:28:57

Depending on how your system behaves you could just wait until core and extra catch up with testing. Alternatively you can downgrade - it is all in the wiki

BTW, shaman hasn't worked for me for bloody yonks!

flamelab · 2010-02-12 15:33:49

For now, in order to use shaman, you should build libaqpm-git and shama2-svn with this PKGBUILD::

pkgname=shaman2-svn
pkgver=1088289
pkgrel=1
pkgdesc="Pacman frontend based on kdelibs and libaqpm - SVN build"
url="http://chakra-project.org/tools-shaman.html"
license="GPL"
arch=('i686' 'x86_64')
depends=('pacman' 'kdelibs' 'dbus' 'libaqpm-git')
makedepends=('subversion' 'cmake')
provides=('shaman')
conflicts=('shaman')
source=()
md5sums=()

_svnmod="shaman"
_svntrunk="svn://anonsvn.kde.org/home/kde/trunk/playground/sysadmin/shaman"

build() {
    cd $startdir/src
    msg "Connecting to the SVN server...."
    svn co $_svntrunk $_svnmod

    [ -d ./$_svnmod-build ] && rm -Rf ./$_svnmod-build
    cp -r ./$_svnmod ./$_svnmod-build
    cd ./$_svnmod-build

    msg "SVN checkout done or server timeout"
    msg "Starting cmake..."

    cmake . -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=RelWithDebInfo || return 1

    msg "Starting make..."

    make || return 1
    
    msg "Make successful, installing..."
    
    make DESTDIR=${pkgdir} install || return 1
    }

jowilkin · 2010-02-12 22:46:27

jumbotron wrote:

hi fellows...this one is the last i bother{i hope so:lol:] btw i stop use [testing] repo:

# pacman -Su
:: Starting full system upgrade...
warning: cryptsetup: local (1.1.0-2) is newer than core (1.1.0-1)
warning: device-mapper: local (2.02.60-3) is newer than core (2.02.60-2)
warning: filesystem: local (2010.02-1) is newer than core (2010.01-1)
warning: lvm2: local (2.02.60-3) is newer than core (2.02.60-2)
warning: mkinitcpio: local (0.5.99.5-1) is newer than core (0.5.30-1)
warning: rp-pppoe: local (3.10-3) is newer than core (3.10-2)
warning: tcp_wrappers: local (7.6-11) is newer than core (7.6-10)
 local database is up to date

how can i handle it?

Did you use testing to update and then disable testing? There are 2 options: 1) if you aren't having any problems, just accept the warnings and eventually they will go away when the testing packages move into the core repo, 2) downgrade the packages to the versions in core right now.

To accomplish 2, just run pacman -Syuu

hermit · 2010-02-19 16:30:27

==>  Continue the building of shaman ? [Y/n]
==>   ----------------------------------------------
==>y


==> Install or build missing dependencies for shaman:
==> Building and installing package

==> shaman dependencies:
 - aqpm (already installed)
 - aqpm (already installed)
 - cmake (already installed)
 - automoc4 (already installed)
==> Making package: shaman 1.2.1-1 i686 (Fri Feb 19 10:22:38 CST 2010)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
  -> Found shaman-1.2.1.tar.gz in build dir
==> Validating source files with md5sums...
    shaman-1.2.1.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error: Makepkg was unable to build shaman package.

any idea?

tomk · 2010-02-19 17:11:17

The error message is quite clear - the shaman source tarball did not pass the validity check. Either your download is corrupted, or the PKGBUILD md5sum is incorrect.

Error messages are there to help you - it is advisable to read them, not just post them here.

Allan · 2010-02-20 00:35:18

And it does not matter anyway... shaman(v1) will not build and is unsupported upstream. shaman2-svn is the only "working" shaman, but it is pre-alpha... use at your systems risk.

pjezek · 2010-05-05 09:57:01

As perhaps a last note to this thread: Pacman is a pretty great design but it can't show a list of pkgs by their amount of data. When one wants to manage his/her arch system properly, takes care about partition usage and about unused or functionally redundant pkgs. That's why some people search frontends with the feature I write about... Not GUI but missing function of pacman is the matter...

Arch Linux

#1 2010-02-10 23:42:45

shaman doesn't show...

#2 2010-02-11 00:22:58

Re: shaman doesn't show...

#3 2010-02-11 01:18:28

Re: shaman doesn't show...

#4 2010-02-11 01:39:53

Re: shaman doesn't show...

#5 2010-02-11 15:25:54

Re: shaman doesn't show...

#6 2010-02-11 15:55:55

Re: shaman doesn't show...

#7 2010-02-11 19:49:50

Re: shaman doesn't show...

#8 2010-02-11 19:57:11

Re: shaman doesn't show...

#9 2010-02-12 15:23:59

Re: shaman doesn't show...

#10 2010-02-12 15:28:57

Re: shaman doesn't show...

#11 2010-02-12 15:33:49

Re: shaman doesn't show...

#12 2010-02-12 22:46:27

Re: shaman doesn't show...

#13 2010-02-19 16:30:27

Re: shaman doesn't show...

#14 2010-02-19 17:11:17

Re: shaman doesn't show...

#15 2010-02-20 00:35:18

Re: shaman doesn't show...

#16 2010-05-05 09:57:01

Re: shaman doesn't show...

Board footer