[Sugar-devel] Browse Failed to Start
When attempting to open Browse on a Fedora 23 machine, I receive the error that "Browse Failed to Start" I recently pulled and built the most updated sugar source, and it seems that some features, specifically network related features are outputting this error. Regardless, I am pasting the links below to the errors from logs. org.laptop.WebActivity-1.log: http://pastebin.com/raw.php?i=PgnPptGA org.laptop.Log-1.log: http://pastebin.com/raw.php?i=4McEGjey Thanks ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Error while setting up sugar-build
Yes, you could rework the pull request by Daksh in response to review comments by Sam. If you do this, keep the author as Daksh, which you can do with git commit --author. https://github.com/sugarlabs/sugar-build/pull/34 On Wed, Nov 25, 2015 at 04:00:51AM +0530, Utkarsh Tiwari wrote: > Hi, > I was trying to setup sugar-build on my Ubuntu 14.04 when I ran > into this error - > https://paste.fedoraproject.org/294173/84020201/ . > To fix this i had to change the distro version in the root.json file. > Should I create a pull request for this? > > regards, > Utkarsh Tiwari > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Error while setting up sugar-build
Hi, I was trying to setup sugar-build on my Ubuntu 14.04 when I ran into this error - > https://paste.fedoraproject.org/294173/84020201/ . To fix this i had to change the distro version in the root.json file. Should I create a pull request for this? regards, Utkarsh Tiwari ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ./osbuild shell not valid command
I'd like to see *.spec.in and a debian equivalent hosted in the upstream repositories, along with README files that explain how to make packages from the repositories. However, I don't see the need for COPR, automatic test suites, or other automata. These automata obscure the process and lead to silos of expertise, and when people move on the remaining automata fall down. I'd prefer to reduce complexity rather than increase it, giving more time for people to hack on the actual code. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] AbiWord 3.next release plans
Hi Hubert, I cloned the abiword repository (r35148) and built abiword with the following options: ./configure --enable-collab-backend-sugar --enable-plugins="collab" This triggers no compilation errors, only deprecation warnings about Gtk. The gtk deprecations are from the zebra striping (gtk_tree_view_set_rules_hint), which has been removed from gtk so it doesn't want that hint any more. (Removing the zebra striping needed like a massive announcement, but it didn't seem to get any). You can remove those 2 calls to gtk_tree_view_set_rules_hint in the collab code and it still runs fine. Only the "service" backend depends on GNU tls. I believe that this is the abicollab.net backend, but I'm not sure. This seems to indicate that the sugar backend is ok for now, and that's the backed that bothers me. Thanks, Sam On Mon, Nov 23, 2015 at 2:36 PM, Hubert Figuière wrote: > On 22/11/15 06:25 PM, Martin Edmund Sevior wrote: > > > Sorry for not responding sooner. In general Hub I agree with your > > plans for abiword-3.1 however I would vote against depreciating the > > abicollab plugin. The abicollab.net service is up and running though > > I don’t know how much longer Marc Maurer will maintain it. > > Now I have another problem about that service: I don't even have the > possibility to install a server, even to test. > So maybe there need to be a plan for that. > > > I didn't realise the gnutls API had changed. I don’t know if I'll get > > the time to fit it for GNUtls > 3.4 but I'd like to see if get it > > running again. > > They have changed for quite a while. We got compilation warnings for a > bit. Like the collab plugin trigger a good bunch of Gtk deprecation > warnings that needs to be fixed... > > > Hub > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ./osbuild shell not valid command
I'm suggesting that the COPR be created with the username SugarLabs with access granted as needed. I'm in no position to act on SL behalf, that would need to come from the powers that be, I don't want to step on any toes. That way it would be "dnf copr enable SugarLabs/sugar" and not someones personal account in the docs and public archives. Oh yea, you could do some integration where a commit occurs and a rpm pops out. ;) Just my take on things, Jerry > On November 24, 2015 at 2:24 AM "Sam P." wrote: > > > Hi Jerry, > > A COPR would be amazing! I think that it would be amazing to have a set > of > rpms for the master branch automatically built. > > But I think there is still a role for sugar-build for like building and > developing :) It's very bad for testing though. > > Re the test suite: good idea. I have no idea why it doesn't run now and > I > don't have the time to dive into it now. > > Thanks, > Sam > > On Tue, Nov 24, 2015 at 7:07 PM, Jerry Vonau wrote: > > > Sam/others who might chime in. > > > > There has to be a better way than that, in the past there was automatic > > testing that replied on COPR(a web based rpm build system for Fedora) > > building the rpms. What is missing from git for packaging is a rpm > > spec.in > > for Fedora and whatever Debain uses that could be set via the Makefile, > > officially blessed by SugarLabs for other developers. Fedora has their > > spec > > file under git control for their release purposes, same holds true at > > OLPC > > where rpms are created for the XO's use but there is no reason not to > > have > > the packaging files freely available anyway, with that in place > > generating > > rpm out of git becomes so much easier. This will greatly help with > > testing > > as then anybody can now point COPR at their own git repo to generate a > > snapshot and build the rpms to test without having to roll the source > > rpm > > first. All you need to do is dnf enable your own copr repo and dnf > > update > > and test away like how I tested the issues with F23. Now making things > > easier for everybody should help trying to make sugar better, that is > > the > > objective right? It opens the possibility that someone can resurrect > > the > > automatic test suite that was in place in the past working again. > > > > Jerry > > > > > On November 23, 2015 at 8:33 PM Free Dom > > > wrote: > > > > > > > > > Is there an alternative since I am on Fedora 23? > > > > > > On Mon, Nov 23, 2015 at 8:32 PM, Free Dom > > > > > > wrote: > > > > > > > I am on Fedora 23. > > > > > > > > ./osbuild shell > > > > > > > > > > > > On Mon, Nov 23, 2015 at 8:28 PM, Sam P. wrote: > > > > > > > >> Hi, > > > >> > > > >> What distribution are you on? I don't know if osbuild shell works > > > >> on > > > >> fedora because broot is not used. > > > >> > > > >> You should be able to not use the shell though. Eg. ./osbuild > > > >> run, > > > >> ./osbuild pull, ./osbuild build, etc. > > > >> > > > >> Thanks, > > > >> Sam > > > >> > > > >> On Tue, Nov 24, 2015, 1:25 PM Free Dom > > > >> > > > >> wrote: > > > >> > > > >>> I am getting this error every time I attempt to run ./osbuild > > > >>> shell > > > >>> from > > > >>> the guide at > > > >>> https://developer.sugarlabs.org/dev-environment.md.html > > > >>> > > > >>> > > > >>> Is there a dependency I am missing? > > > >>> ___ > > > >>> Sugar-devel mailing list > > > >>> Sugar-devel@lists.sugarlabs.org > > > >>> http://lists.sugarlabs.org/listinfo/sugar-devel > > > >>> > > > >> > > > > > > > ___ > > > Sugar-devel mailing list > > > Sugar-devel@lists.sugarlabs.org > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ./osbuild shell not valid command
Hi Jerry, A COPR would be amazing! I think that it would be amazing to have a set of rpms for the master branch automatically built. But I think there is still a role for sugar-build for like building and developing :) It's very bad for testing though. Re the test suite: good idea. I have no idea why it doesn't run now and I don't have the time to dive into it now. Thanks, Sam On Tue, Nov 24, 2015 at 7:07 PM, Jerry Vonau wrote: > Sam/others who might chime in. > > There has to be a better way than that, in the past there was automatic > testing that replied on COPR(a web based rpm build system for Fedora) > building the rpms. What is missing from git for packaging is a rpm spec.in > for Fedora and whatever Debain uses that could be set via the Makefile, > officially blessed by SugarLabs for other developers. Fedora has their spec > file under git control for their release purposes, same holds true at OLPC > where rpms are created for the XO's use but there is no reason not to have > the packaging files freely available anyway, with that in place generating > rpm out of git becomes so much easier. This will greatly help with testing > as then anybody can now point COPR at their own git repo to generate a > snapshot and build the rpms to test without having to roll the source rpm > first. All you need to do is dnf enable your own copr repo and dnf update > and test away like how I tested the issues with F23. Now making things > easier for everybody should help trying to make sugar better, that is the > objective right? It opens the possibility that someone can resurrect the > automatic test suite that was in place in the past working again. > > Jerry > > > On November 23, 2015 at 8:33 PM Free Dom > > wrote: > > > > > > Is there an alternative since I am on Fedora 23? > > > > On Mon, Nov 23, 2015 at 8:32 PM, Free Dom > > wrote: > > > > > I am on Fedora 23. > > > > > > ./osbuild shell > > > > > > > > > On Mon, Nov 23, 2015 at 8:28 PM, Sam P. wrote: > > > > > >> Hi, > > >> > > >> What distribution are you on? I don't know if osbuild shell works on > > >> fedora because broot is not used. > > >> > > >> You should be able to not use the shell though. Eg. ./osbuild run, > > >> ./osbuild pull, ./osbuild build, etc. > > >> > > >> Thanks, > > >> Sam > > >> > > >> On Tue, Nov 24, 2015, 1:25 PM Free Dom > > >> wrote: > > >> > > >>> I am getting this error every time I attempt to run ./osbuild shell > > >>> from > > >>> the guide at https://developer.sugarlabs.org/dev-environment.md.html > > >>> > > >>> > > >>> Is there a dependency I am missing? > > >>> ___ > > >>> Sugar-devel mailing list > > >>> Sugar-devel@lists.sugarlabs.org > > >>> http://lists.sugarlabs.org/listinfo/sugar-devel > > >>> > > >> > > > > > ___ > > Sugar-devel mailing list > > Sugar-devel@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] ./osbuild shell not valid command
Sam/others who might chime in. There has to be a better way than that, in the past there was automatic testing that replied on COPR(a web based rpm build system for Fedora) building the rpms. What is missing from git for packaging is a rpm spec.in for Fedora and whatever Debain uses that could be set via the Makefile, officially blessed by SugarLabs for other developers. Fedora has their spec file under git control for their release purposes, same holds true at OLPC where rpms are created for the XO's use but there is no reason not to have the packaging files freely available anyway, with that in place generating rpm out of git becomes so much easier. This will greatly help with testing as then anybody can now point COPR at their own git repo to generate a snapshot and build the rpms to test without having to roll the source rpm first. All you need to do is dnf enable your own copr repo and dnf update and test away like how I tested the issues with F23. Now making things easier for everybody should help trying to make sugar better, that is the objective right? It opens the possibility that someone can resurrect the automatic test suite that was in place in the past working again. Jerry > On November 23, 2015 at 8:33 PM Free Dom > wrote: > > > Is there an alternative since I am on Fedora 23? > > On Mon, Nov 23, 2015 at 8:32 PM, Free Dom > wrote: > > > I am on Fedora 23. > > > > ./osbuild shell > > > > > > On Mon, Nov 23, 2015 at 8:28 PM, Sam P. wrote: > > > >> Hi, > >> > >> What distribution are you on? I don't know if osbuild shell works on > >> fedora because broot is not used. > >> > >> You should be able to not use the shell though. Eg. ./osbuild run, > >> ./osbuild pull, ./osbuild build, etc. > >> > >> Thanks, > >> Sam > >> > >> On Tue, Nov 24, 2015, 1:25 PM Free Dom > >> wrote: > >> > >>> I am getting this error every time I attempt to run ./osbuild shell > >>> from > >>> the guide at https://developer.sugarlabs.org/dev-environment.md.html > >>> > >>> > >>> Is there a dependency I am missing? > >>> ___ > >>> Sugar-devel mailing list > >>> Sugar-devel@lists.sugarlabs.org > >>> http://lists.sugarlabs.org/listinfo/sugar-devel > >>> > >> > > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
