Jump to content

kendew

Members
  • Content count

    177
  • Joined

  • Last visited

  • Days Won

    1

kendew last won the day on July 19 2014

kendew had the most liked content!

Community Reputation

2 Neutral

1 Follower

About kendew

  • Rank
    Member
  1. kendew

    How to install Moksha on Arch Linux and derivatives

    No, not in PKGBUILD. For PKGBUILD I was referring to having elementary as dependency. However, if you try to build via the AUR yaourt moksha there is this comment with a server line. I thought you would probably like to update it. Thanks for your hard work.
  2. kendew

    How to install Moksha on Arch Linux and derivatives

    Thank you Fusion809 for making an appearance here. That's the kind of error I got when I tried to build using yaourt after editing PKGBUILD to eliminate requirement for elementary as I mentioned above, something about unable to find part base. Fusion809, are you the person maintaining that AUR package? If so, perhaps you could edit PKGBUILD. At the moment for a fresh Moksha install in Arch or Manjaro the elementary dependency cannot be satisfied as it seems elementary is no longer available in AUR. Jeff has said it isn't needed for the latest build. Also, perhaps update the server line there too? Thanks for all you are doing. Kendew
  3. kendew

    How to install Moksha on Arch Linux and derivatives

    Just to clarify birdmun, did you also try with pacman with the server line from fusion809 you gave in your VM? I followed my own suggestion editing PKGBUILD in yaourt deleting the requirement for elementary. The build was almost successful, but in the end failed. Perhaps that moksha version 0.2.0-1 still requires elementary. Anyway, I've emailed Brenton, who maintains the AUR package and if I hear anything I'll report back here. Otherwise, for the time being, I'm afraid Arch or Manjaro people will have to wait, or I'll have to hone my Arch skills further and try to build from source. Kendew
  4. kendew

    How to install Moksha on Arch Linux and derivatives

    Sorry birdmun, but that server link just isn't valid. No need to try through pacman.conf, just put in a browser and see, you get a 404 error, unless you know some magic I don't. I tried building moksha through the AUR on a different computer that has Manjaro installed yesterday. The build failed because the build requires a dependency, elementary, which is no longer there in AUR. Jeff has said above that we shouldn't need elementary anymore, and he should know. One guess is that elementary was removed for this reason but the script to build wasn't updated to accommodate this change. So elementary is still required but not needed. I think, birdman, if you are using yaourt you are probably getting moksha from the AUR. Your elementary dependency had already been satisfied when you originally installed. Something has changed since then. I have had no problem updating moksha on machines where it was installed before because the elementary dependency had already been satisfied. My bet is that if you tried to install moksha on a completely fresh install of either Arch or Manjaro it would fail. Please research was yaourt does. It goes through the process of building packages. Basically it's giving you an automated way of building packages Ubuntu seems to lack. With yaourt you get asked questions about building and offered chances to edit. Come to think of it, maybe I could edit out the elementary dependency, worth a try to polish my beginner Arch skills. Worth a try until someone fixes it. The beauty of what fusion809 did was to offer a repository where we wouldn't need to build package through yaourt. We could simply install through pacman. But he must have either moved or removed the packages. No disrespect intended here. Just trying to get at the truth and figure out what's going on.
  5. kendew

    How to install Moksha on Arch Linux and derivatives

    @birdman and anybody Why do you think you are accessing moksha via fusion809. You say you are using yaourt. That accesses AUR which contains moksha. As of my understanding, and my experience with Arch just begun this year, so still new to it, adding fusion809's server line should make moksha available via pacman, not yaourt. Yaourt is for AUR. (See quote below). Go to https://github.com/fusion809/PKGBUILDs and within PKBUILDs there is no longer any directory called releases that I see. If I try "yaourt moksha" today I see an old message (March 10): That server location is the same as at the beginning of that post. Anyway, today I don't see yaourt insisting on elementary as a dependency, so maybe it's working now, as Jeff suggested above. Actually, I need it for installation on a different computer and after I get a chance to try it, I'll be reporting back. But unless we get word from fusion809, I wouldn't try that route. I really think fusion809 is great in providing us with the opportunity to go directly through pacman and am really grateful to him for that, but if things change it would be nice if we were informed. Kendew
  6. kendew

    How to install Moksha on Arch Linux and derivatives

    Well, something's changed recently. The server line above isn't working now. Also, can't install Moksha now in Arch because the dependency elementary can no longer be found, nor with pacman. Installed Moksha fine just the other day on a box running Manjaro. Any updates in the making or workarounds?
  7. kendew

    Possible to share /home??

    Hi I have the opportunity to try to install Bodhi next to another Linux distribution called Manjaro. I would like the user of the computer to be able to use either Bodhi or Manjaro, but to share the same /home directory. That way, users could have all their files available whichever OS they choose. Is this possible? If so, how? Kendew
  8. kendew

    Stuck trying to install Moksha on Debian 8

    Well, no longer stuck. Yesterday I compiled and installed Moksha per Jeff's instructions exactly on a fresh Debian 8 install and it all went smooth as silk, though there seem to be a couple of modules missing that are found in the regular Bodhi install. There must have been some sort of software conflict on my previous attempts that were not present with the fresh install. So message from this is Jeff's instructions do work -- just have to get the conditions right. ​ ​I may get into creating deb packages at some point. But how to uninstall? Just rm -r appropriate directories? And what would those directories be? ​Also, Jeff, just curious, you spoke of segfaults -- which versions of these packages does the latest Bodhi use? You wrote those instructions some time ago. ​ ​I'm eager to try to take Moksha further on Debian. I'd like to know what other packages are worth trying to install. I also might like to try my hand at creating an original Moksha theme as well. I'll need to do some research to figure out how to do that.
  9. kendew

    Stuck trying to install Moksha on Debian 8

    Certainly I'll be installing Bodhi for computers that go away from my circle of influence. There are many reasons to do so. Bodhi 3.2 is really solid. Ubuntu as a base is way more user friendly than Debian, and for a lot of people who don't even have a good idea of what open source is when they get the computer I don't have to explain what, say, Ice Weasel is or how to use WICD. They're already usually familiar with Firefox and like a wireless interface where they don't have to know about hex values or WPA are. But for me, on my own computer, I like to be versatile and try different things, see what's worthwhile. The fact two other people told me they installed Moksha on Debian is enough to make me want to do it too. That being said, just to be honest there was a time in Bodhi's development when it wasn't working for me, as Bodhi 3 was emerging. I didn't like a lot about E19. Also someone donated to our non-profit a bunch of old Dell Inspiron laptops and Bodhi 3 wasn't working well with the gma500 chip on those computers but Debian did. I haven't really had the time to research why, so I just stuck with what worked. Since I've been impressed with what Moksha has developed into. Things I didn't like about E19 are gone. Since I have several Debian systems set up I'd be interested if I could get Moksha working on them rather than wipe and install a new system. Curiously Bodhi 3.2 still doesn't work well with that Inspiron sound chip, though I've sense found a workaround. I'm really happy with Bodhi and the Moksha development. I would like to see if I could get Moksha to be more graphically appealing for me. One of the things I liked about E17 was the aesthetic diversity that was possible. Your work has been much appreciated here.
  10. kendew

    Stuck trying to install Moksha on Debian 8

    So getting ready to try this. Usually when I install Debian I install without any Desktop Environment whatever -- no Gnome, LXDE, etc., and begin with CLI. This helps insure no DE conflicts. I'll then need to install a simple DE, usually Openbox, so I can run a web browser and get to Jeff's instruction page. I have a question. For best Moksha results, should I compile EFL and Elementary versions as per instructions, which is efl-1.15.1, etc. Or should I go with latest versions, such as efl-1.17.0? What about Moksha? Once compiled and installed is there a way for these packages to be upgraded? Thanks
  11. kendew

    Stuck trying to install Moksha on Debian 8

    @Jeff, Yes to both questions. On the second computer I was following your instructions exactly. ​ ​Perhaps there is some conflict with other software. Or perhaps my failures burnt some bridges. In any case, when I get the chance, I plan to try compiling on a fresh Deb 8 install on a different computer. ​I'll report results back here. E17 from the Debian repositories works fine.
  12. kendew

    Stuck trying to install Moksha on Debian 8

    I'm glad it's working for some people. Tried on a Debian 8 instalallation on a different computer but got the same error compiling elementary. make all-recursive make[1]: Entering directory '/root/elementary-1.15.1' Making all in src make[2]: Entering directory '/root/elementary-1.15.1/src' Making all in lib make[3]: Entering directory '/root/elementary-1.15.1/src/lib' EOLIAN elm_access.eo.c /bin/bash: line 2: 26204 Segmentation fault /usr/bin/eolian_gen --eo --legacy -I//usr/share/eolian/include/eo-1 -I//usr/share/eolian/include/evas-1 -I//usr/share/eolian/include/edje-1 -I//usr/share/eolian/include/ecore-1 -I//usr/share/eolian/include/efl-1 -I../../src/lib --gc -o elm_access.eo.c elm_access.eo Makefile:2644: recipe for target 'elm_access.eo.c' failed make[3]: *** [elm_access.eo.c] Error 139 make[3]: Leaving directory '/root/elementary-1.15.1/src/lib' Makefile:424: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/root/elementary-1.15.1/src' Makefile:618: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/root/elementary-1.15.1' Makefile:501: recipe for target 'all' failed make: *** [all] Error 2 Seems to hit a segmentation fault, and I'm not sure what that is or how to get around it. Perhaps I'll have to try on a fresh Debian install. Grateful to hear Moksha on Debian working out for some people and maybe one day myself will be included. E17 install works fine. I'll check Jazz's suggestion too. For myself, I like Debian but I think I'd go with Bodhi for general installation for others. I have been using LXQt on Debian and recently xscreensaver kicked up a fuss because Debian 8 (stable) hadn't upgraded to its latest version. In an effort to be stable Debian can be strict. This has caused some confusion for some I installed that combination for. Good luck, Randy. I'll continue working on this.,
  13. kendew

    Stuck trying to install Moksha on Debian 8

    Think I'm going to have to try this on a different Debian 8 system. Failed again on make: ​ make all-recursive make[1]: Entering directory '/root/elementary-1.15.1' Making all in src make[2]: Entering directory '/root/elementary-1.15.1/src' Making all in lib make[3]: Entering directory '/root/elementary-1.15.1/src/lib' EOLIAN elm_access.eo.c /bin/bash: line 2: 6403 Segmentation fault /usr/bin/eolian_gen --eo --legacy -I//usr/share/eolian/include/eo-1 -I//usr/share/eolian/include/evas-1 -I//usr/share/eolian/include/edje-1 -I//usr/share/eolian/include/ecore-1 -I//usr/share/eolian/include/efl-1 -I../../src/lib --gc -o elm_access.eo.c elm_access.eo Makefile:2644: recipe for target 'elm_access.eo.c' failed make[3]: *** [elm_access.eo.c] Error 139 make[3]: Leaving directory '/root/elementary-1.15.1/src/lib' Makefile:424: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/root/elementary-1.15.1/src' Makefile:618: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/root/elementary-1.15.1' Makefile:501: recipe for target 'all' failed make: *** [all] Error 2 ​Also tried installing E17 through Synaptic. E17 works but still couldn't compile Moksha. ​@Randy, Just curious, why did you install Moksha on Debian 8? Does it work as well as Bodhi's Moksha on Ubuntu 14?
  14. kendew

    Stuck trying to install Moksha on Debian 8

    Randy, thanks for replying. You've told me something important! You installed Moksha today, and used Jeff's instructions on Debian 8. This tells me that the instructions and versions are not outdated and that it does indeed work for someone on same Debian OS. That saves me a lot of guessing. I'm going to try again tomorrow and see how it goes...
  15. kendew

    Stuck trying to install Moksha on Debian 8

    ​EFL seemed to compile and install well. Elementary, the second part of Step 2 is where the above hiccup occurred. However, I want to try this again paying closer attention to what I'm doing and taking a more careful approach rather than simply copying and pasting commands. ​So to start with, looking at the index I'm seeing far newer versions of EFL than version 1.15.1 which must have been the latest version on November 4, 2015 when Jeff's instructions were written. The first thing I'm wondering is if I should use those newer versions, say efl-1.19.5? ​The second thing I'm wondering is if, should that fail, I install Debian 8's repository version of E17 and then simply try Step 3 & 4 compiling and installing Moksha and profile data, skipping Step 2. ​All in all I'd love to get Moksha running on Debian 8 as I'm using LXQt at the moment. ​Grateful for assistance. ​ ​
×