Late review of this meeting, sorry.
I'm concerned about the idea to use 15 icons. I've seen your private
branch changes to the Sugar Artwork module. I think this is the wrong
approach, as you are using many separate SVG files to render only two
dimensions; disk space and number of journal
Good. Your test result and traceback shows that GIR for WebKit2 is
not available.
/boot/olpc_build is created by olpc-os-builder when an operating
system image is prepared. It contains text that identifies the
release.
Here's what I've got in a lab laptop; "13.2.10 for XO-4 (build 22)"
The
Interesting, thanks. Perhaps this error was caused by inadequate
testing of 62cc314. See also
https://github.com/sugarlabs/sugar-artwork/issues/109
You're welcome to work on it, otherwise as Aniket says, starting with
a clean repository workspace should help.
If "make clean" doesn't fix it,
Sent the email to debian-de...@lists.debian.org as well.
On Fri, Jul 5, 2019 at 4:13 PM ANIKET MATHUR wrote:
> Sent an email to the Debian user mailing list debian-u...@lists.debian.org
> requesting
> for packaging v0.114.
>
> Packaging of Sugar-toolkit-gtk3 (sugar3) v0.114.
> ANIKET MATHUR
>
Try deleting the existing file and then running ./autogen.sh
On Fri, Jul 5, 2019 at 8:14 PM Swarup N wrote:
> Hello,
>
> I was able to establish collaboration by creating two new VM's and
> installing Sugar via the Live Build method.I used an already available .iso
> Sugar file, however it is
Hello,
I was able to establish collaboration by creating two new VM's and
installing Sugar via the Live Build method.I used an already available .iso
Sugar file, however it is v0.112.
In order to upgrade to v0.114, I entered the */usr/src/* directory where
all the 5 sugar modules are present. In
Sent an email to the Debian user mailing list
debian-u...@lists.debian.org requesting
for packaging v0.114.
Packaging of Sugar-toolkit-gtk3 (sugar3) v0.114.
ANIKET MATHUR
4:10 PM (2 minutes ago)
to debian-user
G'day,
Aniket Mathur this side, an active contributor of Sugarlabs as well as a
GSoC
Sorry for not providing the logs (thought I have provided them earlier).
Here are the logs:
https://paste.fedoraproject.org/paste/ro44qwtkw99SYY2acA3lPg
Update: I created the file olpc_build and now Sugar works. Thanks alot!
On Fri, Jul 5, 2019 at 2:58 PM James Cameron wrote:
> Still, you have
Still, you have not shown us the error. Why not? Haven't you looked
at the cause yet? You really should do all you can to solve each
problem you face.
I'll have to speculate.
Sugar 0.112 src/jarabe/view/viewhelp.py line 38 onwards does import
WebKit if the system is recognised as OLPC OS
On a new VM I created yesterday, I didn't have the booting problem. I did
add http://rpmdropbox.laptop.org/f18/ as a repository and I installed
Sugar (and its dependencies) from that repo. It seems that WebKit/2 is not
properly installed or I must've done something wrong. Shell.log only has
one
The error about unity-settings-daemon can be ignored. It is caused by
OLPC customised /usr/bin/sugar which checks for systems with DMI BIOS
version data. You can see this by comparing /usr/bin/sugar with
the v0.112 bin/sugar.in on GitHub.
Yes, WebKit or WebKit2 is required.
You have a new
Interesting that you've tried to install from the repository using a
URL.
You must have missed adding the yum repository to /etc/yum.repos.d,
because had you done that the dependency resolution would have been
automatic.
You can see gwebsockets in the repository.
On Wed, Jul 03, 2019 at
I went through Nikhil's weekly blogs, also viewed some of his pull requests
and tried to understand the changes.
Seems like Nikhil is doing a great job. :-)
On Tue, Jul 2, 2019 at 3:47 AM Rahul Bothra wrote:
> G'day,
>
> We've completed the first set of evaluations for all GSoC projects. Since
13 matches
Mail list logo
