> On Sep 29, 2011, at 5:47 AM, michael bouchaud wrote: > >> 2011/9/28 mh <mhe...@member.fsf.org> >> >>> >>> On Sep 28, 2011, at 9:25 AM, michael bouchaud wrote: >>> >>>> 2011/9/20 P Purkayastha <ppu...@gmail.com> >>>> >>>>> >>>>> On Tuesday, September 20, 2011 10:55:31 AM UTC+8, mh wrote: >>>>>> >>>>>> Ah, broken package. It was suggested to me to subscribe to >>>>>> enlightenment-svn mailing list, which I've done. When a possible fix is >>>>>> made, will there be an announcement there so I can know to test it, or >>>>> maybe >>>>>> another list? >>>>>> >>>>>> thanks, >>>>>> >>>>>> mh >>>>>> >>>>> Watch the timeline* time and again ;) >>>>> >>>>> * http://trac.enlightenment.org/e/timeline >>>>> >>>>> >>>>> >>> ------------------------------------------------------------------------------ >>>>> All the data continuously generated in your IT infrastructure contains a >>>>> definitive record of customers, application performance, security >>>>> threats, fraudulent activity and more. Splunk takes this data and makes >>>>> sense of it. Business sense. IT sense. Common sense. >>>>> http://p.sf.net/sfu/splunk-d2dcopy1 >>>>> _______________________________________________ >>>>> enlightenment-users mailing list >>>>> enlightenment-users@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-users >>>>> >>>>> >>>> Hi, sorry to do my answer so late, but some event don't allowed me to do >>> it >>>> sooner. Since yesterday elsa work again, you can type your hostname and >>>> password again. Thanks Raster our superhero. >>>> >>>> -- >>>> Michaël Bouchaud >>> >>> Thanks Michael and SuperRaster! I am able to type hostname and password >>> now, but I have another problem: >>> >>> First, I deleted the old trunk directory and used the build script from >>> http://www.enlightenment.org/p.php?p=contribute&l=en to rebuild all the >>> EFL components, then elementary, then elsa. >>> >>> I am using the elsa init file posted here: >>> http://www.bodhilinux.com/forums/index.php?/topic/2108-how-to-auto-start-elsa/, >>> but I added /usr/local/sbin to the PATH on line 15 and changed the DAEMON >>> path on line 18 to /usr/local/sbin/elsa. >>> >>> After rebooting, elsa starts and I can enter hostname, password, select >>> Enlightenment, and click the drop down check box. The elsa screen goes away >>> and Enlightenment starts. But then I'm returned to the Elsa screen again. I >>> open a terminal (cntl-alt-f1) and list running processes and enlightenment >>> is running. If I go back to the Elsa screen and try to login again it >>> rejects the login. If I try to shutdown, reboot or suspend using the elsa >>> menu box nothing happens. But, if I reboot from the terminal and try to use >>> elsa's menu to reboot before I login, it works fine. >>> >>> Is there something else in the /etc/init.d/elsa file that needs to be >>> changed, or do you think something else is wrong? Or is there a different >>> init file I should be using. >>> >>> e-version is 63642, amd64. >>> >>> thanks! >>> >>> mh >>> >>> >> >> This is very strange because elsa if she restarts kills X before, to clean >> the place. But you still have your session open. I will try to reproduce, >> but the code looks good and this not depending on your script. >> I have made a packaging for debian with the contribution of another frenchy >> who has writed this script. And it works fine here on a squeeze install. You >> find it in the svn at this place trunk/packaging/debian/extras/elsa >> >> -- >> Michaël Bouchaud > > Something else I tried: I added a new user and then used elsa to login. E > started and went through the initial configuration, step by step. When the > configuration finished, the display went back to elsa , and e was still > running. Don't know if that helps. > > I checked out the new debian package in svn from > trunk/packaging/debian/extras/elsa, thanks! I'm ok installing from svn with > the autogen.sh and so on. But I'm not sure how to proceed from here. > > I'll check on the irc channel and see if I can get some help there now. > > mh
Nothing on irc, but I found the trunk/packaging/debian directory and the README, e17builder.sh script, pbuilder-config and the rest. Read the README, but I've never done this before and I'll probably muck things up trying. But I'm more than willing to learn. I made the directory ~/.pbuilderrc and copied pbuilder-config and e17builder.sh there. Opened the script but right away I think there's a problem because I don't have an esvn username. I have the new files from trunk/packaging/debian/extras/elsa already, so can I just put them in ~/repository_folder and comment out the lines from username="USERNAME" to localpath="$HOME/repository_folder"? I assume I can also comment out all the distros and architectures except mine. Also assume I can comment out all the things to compile, eina… and add elsa? I'm using Debian sid, so I'd need to replace /usr/share/cdbootstrap/suites with the suites file? Oh, and install pbuilder and all the dependencies first. Probably not even close on this, but what the hell. mh ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
