LinuxQuestions.org - [SOLVED] problems with radiotray from slackbuilds

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - problems with radiotray from slackbuilds (https://www.linuxquestions.org/questions/slackware-14/problems-with-radiotray-from-slackbuilds-4175448550/)

problems with radiotray from slackbuilds

hi

i'm on a 14 full install

with sbopkg installed all the required deps > gst-ffmpeg gst-plugins-ugly gst-python > all went ok

when i try to finally install radiotray i get this

Code:

Traceback (most recent call last):

  File "setup.py", line 16, in <module>

    from src.lib.common import APPNAME, APPVERSION

  File "/tmp/SBo/radiotray-0.7.2/src/lib/common.py", line 5, in <module>

    from xdg.BaseDirectory import xdg_data_home

ImportError: No module named xdg.BaseDirectory



radiotray:

Would you like to continue processing the rest of the

queue or would you like to abort?  If this failed

package is a dependency of another package in the queue

then it may not make sense to continue.



(Y)es to continue, (N)o to abort, (R)etry the build?:

on yes

Code:

SUMMARY LOG

Using the SBo repository for Slackware 14.0

Queue Process:  Download, build, and install



radiotray:

  MD5SUM check for radiotray-0.7.2.tar.gz ... OK

  Error occurred with build.  Please check the log.

the log just report what i have already write bout the import error...

any clue?

thnx a lot

you probably need also pyxdg.

Quote:

Originally Posted by ponce (Post 4884075)

you probably need also pyxdg.

thnx a lot ponce, that works...

Code:

SUMMARY LOG                                                                                                                      │

│ Using the SBo repository for Slackware 14.0                                                                                      │

│ Queue Process:  Download, build, and install                                                                                    │

│

│ radiotray:                                                                                                                      │

│  MD5SUM check for radiotray-0.7.2.tar.gz ... OK                                                                                │

│  Building package radiotray-0.7.2-x86_64-1_SBo.tgz ... OK                                                                      │

│  Installing package radiotray-0.7.2-x86_64-1_SBo.tgz ... OK                                                                    │

│

│ +++++++++++++++++++++++++++++++++++++++++++                                                                                      │

│

│ ###########################################                                                                                      │

│          Queue process complete!                                                                                                │

│ ###########################################

but now i'm in trouble with actually run it

Code:

bash-4.2$ radiotray

Traceback (most recent call last):

  File "/usr/bin/radiotray", line 12, in <module>

    os.chdir(workdir)

OSError: [Errno 2] No such file or directory: '/usr/bin/src'

dunno, here runs (beside the fact that I don't have a gtk-tray where it can reside -needed).

having a deeper look at this, seems it needs also lxml.

Quote:

Originally Posted by ponce (Post 4884154)

having a deeper look at this, seems it needs also lxml.

thnx ponce

installation of lxml (with the required deps of beautifulsoup) solved the issue

as a note i'm wondering if it's the case to put pyxdg and lxml in the required deps of the radiotray's info file

have a nice day and again thnx for helpin me out

yes, I think it's the case.

you're welcome :)

what is the easy way i can fill a report to slackbuild people to inform bout that?

you can write to the mailing list (slackbuilds-users@slackbuilds.org), cc'ing the maintainer too.

i'll do that

is good if in the mail i put the link to this post to explain the issue (with a brief note) or i have to rewrite all?

thnx

it's ok, but explain also in the mail what has to be fixed, don't force the mailing list subscribers to read all this stuff ;)