[cable_guy]

It's not a python file. the correct way to start it is: ./LaSi.sh
make it executable first with sudo chmod +x LaSi.sh

thanks. sorry. what a bloody noob. I forgot how to execute the thing.

[coupas]

I am trying to get beets to work.. but I am getting:

Code:

Reading package lists... Done
Building dependency tree      
Reading state information... Done
python-pip is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
sudo: invalid option -- 'q'
usage: sudo -h | -K | -k | -L | -V
usage: sudo -v [-AknS] [-p prompt]
usage: sudo -l[l] [-AknS] [-g groupname|#gid] [-p prompt] [-U username] [-u
            username|#uid] [-g groupname|#gid] [command]
usage: sudo [-AbEHknPS] [-C fd] [-g groupname|#gid] [-p prompt] [-u
            username|#uid] [-g groupname|#gid] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-C fd] [-g groupname|#gid] [-p prompt] [-u
            username|#uid] file ...
sudo: beets: command not found

Failed! Installing Beets didn't finish, try again or:
Copy the text above and report an issue at the following address:
https://github.com/Mar2zz/LaSi/issues

I am at the point where I want to remove everything regarding beets and start over.. but I am unsure how to proceed from here.

I was also getting:

Code:

Running setup.py install for beets
    WARNING: beetsplug is a namespace package, but its __init__.py does
    not declare_namespace(); setuptools 0.7 will REQUIRE this!
    (See the setuptools manual under "Namespace Packages" for details.)

when I was trying something else..

Hilfe!

And thanks Adrian for all your hard work, you are a god send.

[oneadvent]

Hey just wanted to say thanks again. I set up a system for my mother in law and this made it brain dead easy.

Thanks!

[Mar2zz]

I am trying to get beets to work.. but I am getting:

Code:

Reading package lists... Done
Building dependency tree      
Reading state information... Done
python-pip is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
sudo: invalid option -- 'q'
usage: sudo -h | -K | -k | -L | -V
usage: sudo -v [-AknS] [-p prompt]
usage: sudo -l[l] [-AknS] [-g groupname|#gid] [-p prompt] [-U username] [-u
            username|#uid] [-g groupname|#gid] [command]
usage: sudo [-AbEHknPS] [-C fd] [-g groupname|#gid] [-p prompt] [-u
            username|#uid] [-g groupname|#gid] [VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-C fd] [-g groupname|#gid] [-p prompt] [-u
            username|#uid] file ...
sudo: beets: command not found

Failed! Installing Beets didn't finish, try again or:
Copy the text above and report an issue at the following address:
https://github.com/Mar2zz/LaSi/issues

I am at the point where I want to remove everything regarding beets and start over.. but I am unsure how to proceed from here.

I was also getting:

Code:

Running setup.py install for beets
    WARNING: beetsplug is a namespace package, but its __init__.py does
    not declare_namespace(); setuptools 0.7 will REQUIRE this!
    (See the setuptools manual under "Namespace Packages" for details.)

when I was trying something else..

Hilfe!

And thanks Adrian for all your hard work, you are a god send.

Fixed it, stupid empty variable, my bad... Download the script again and try again.

Oh and the beetsplug error is something I can't prevent. That's something Adrian Sampson from Beets needs to fix.

[coupas]

Aloha

I am still having some trouble..

Code:

Options:
1. Install Beets
2. Remove Beets
3. Set cronjob for Beets

B. Back to menu
Q. Quit
1

Are you sure you want to continue and install Beets?
[yes/no]: yes

sudo: beets: command not found

Failed! Installing Beets didn't finish, try again or:
Copy the text above and report an issue at the following address:
https://github.com/Mar2zz/LaSi/issues


Press a key to continue

[Mar2zz]

Aloha

I am still having some trouble..

Wow, where was my mind, I forgot the else in an if-construction...
Now it is definitely fixed... Sorry

[coupas]

Works now. Good times. Beets rocks.

[cable_guy]

Hi guys, when installing Maraschino via LaSi, does it install the webserver portion as well? I assume there must be further configuration of some kind required as http://xmbc:7000 doesn't return a website, although Maraschino is started.

[Mar2zz]

Hi I must have missed the email (I subscribed to this topic) and read you posted something here in the Maraschino topic.

LaSi uses the webserver (the cherrypy one) by default and launches it silently. So it must be running on 7000, or else something else is happening. I am using an own version of an init.d script which grabs variables from /etc/default/maraschino, so perhaps you should look there to see if there is another port set.

You could always check with ps aux | grep Maraschino.py to see how and if it is running.

[cable_guy]

hi,

Thanks for the reply.

OK I'm a bit confused. I ran ps aux | grep Maraschino.py and it returned:

xbmc 13270 0.0 0.0 3324 788 pts/0 S+ 21:15 0:00 grep --color=auto Maraschino.py

I don't really understand what that output means tbh, but I assume it's running!

The only thing I can see that I think is wrong, is that in the maraschino settings.py file, the path to the database is listed as "path/to/maraschino.db" . So I assume I need to create the database, any ideas on that please?

[Mar2zz]

I'am sorry, I gave the wrong code, it should be this:

Code:

mars@XBMC:~$ ps aux | grep maraschino-cherrypy.py
mars  1861  1.5  0.5 133672 17280 ?        Sl   22:45   0:04 /usr/bin/python maraschino-cherrypy.py
mars  2165  0.0  0.0   3324   844 pts/0    R+   22:49   0:00 grep --color=auto maraschino-cherrypy.py
mars@XBMC:~$

Kinda strange your settings.py is not edited by my script. Did you use a recent version of LaSi?
If you want to reinstall it, do sudo apt-get purge maraschino, then use LaSi.sh to reinstall, and read terminal output carefully

ps: path/to/database can be anything, as long as you have writeaccess to that folder. I use /home/username/.maraschino/maraschino.db myself.

[cable_guy]

Hi, thanks for your post! I've solved it! I changed the path for the database to what you use, and voila! Maraschino works on port 7000!

I have no idea of which version of LaSi I use, I installed it at Christmas time when I got my 2nd XBMC box.

[Mar2zz]

Hi, thanks for your post! I've solved it! I changed the path for the database to what you use, and voila! Maraschino works on port 7000!

I have no idea of which version of LaSi I use, I installed it at Christmas time when I got my 2nd XBMC box.

Januari the 4th of this year I changed some things in the Maraschino-installer, so that's why your path to database wasn't edited yet I think. If you reinstall in the future it would be better to redownload LaSi.sh and use that one.

Kriss1981 has joined in development of LaSi on FreeBSD, so now some things are changed, the debian/buntu installer is moved to LaSi_Deb.sh, but LaSi.sh downloads that one and executes it (it recognizes which system it's on and downloads the correct installerscript), so you wouldn't really notice the difference.

[cable_guy]

Januari the 4th of this year I changed some things in the Maraschino-installer, so that's why your path to database wasn't edited yet I think. If you reinstall in the future it would be better to redownload LaSi.sh and use that one.

Kriss1981 has joined in development of LaSi on FreeBSD, so now some things are changed, the debian/buntu installer is moved to LaSi_Deb.sh, but LaSi.sh downloads that one and executes it (it recognizes which system it's on and downloads the correct installerscript), so you wouldn't really notice the difference.

Ahh ok I think I must have the old one then. I really love LaSi though, it made things so much easier for me! Thanks for a great product

[Mar2zz]

Glad it's solved, thank you for the heads up