Testing/Reports/Sweets on Raspberry pi armhf raspbian - Revision history

Inkyfingers: edit detail

2012-10-06T11:27:23Z

edit detail

← Older revision		Revision as of 07:27, 6 October 2012
Line 24:		Line 24:
	sudo apt-get install python-vte python-gst0.10 python-pygame python-webkit python-beautifulsoup		sudo apt-get install python-vte python-gst0.10 python-pygame python-webkit python-beautifulsoup

	[[Testing/Reports/Sweets_on_Raspberry_pi_armhf_raspbian#Soft_reboot\|Soft reboot]] the Rasp pi before proceeding.		[[Testing/Reports/Sweets_on_Raspberry_pi_armhf_raspbian#Soft_reboot.\|Soft reboot]] the Rasp pi before proceeding.

	Download the installer,		Download the installer,

Inkyfingers: edit detail

2012-10-06T11:26:23Z

edit detail

← Older revision		Revision as of 07:26, 6 October 2012
Line 34:		Line 34:
	sh installer.sh		sh installer.sh

	Logout of LXDE, then {{Code\|startx}} or [[Testing/Reports/Sweets_on_Raspberry_pi_armhf_raspbian#Soft_reboot\|Soft reboot]] the Rasp pi before proceeding.		Logout of LXDE, then {{Code\|startx}} or [[Testing/Reports/Sweets_on_Raspberry_pi_armhf_raspbian#Soft_reboot.\|Soft reboot]] the Rasp pi before proceeding.

	You can view the sweets help file with this command.		You can view the sweets help file with this command.
Line 87:		Line 87:
	For reference, check the SD card has plenty of space: {{Code\| df -h}}. Reveals Used 2.2G, Avail 1.3G, ok		For reference, check the SD card has plenty of space: {{Code\| df -h}}. Reveals Used 2.2G, Avail 1.3G, ok

	[[Testing/Reports/Sweets_on_Raspberry_pi_armhf_raspbian#Soft_reboot\|Soft reboot]]		[[Testing/Reports/Sweets_on_Raspberry_pi_armhf_raspbian#Soft_reboot.\|Soft reboot.]]

	Now launch again with same command		Now launch again with same command

Inkyfingers: edit detail

2012-10-06T11:15:46Z

edit detail

← Older revision		Revision as of 07:15, 6 October 2012
Line 24:		Line 24:
	sudo apt-get install python-vte python-gst0.10 python-pygame python-webkit python-beautifulsoup		sudo apt-get install python-vte python-gst0.10 python-pygame python-webkit python-beautifulsoup

	[[#~~Soft reboot~~\|Soft reboot]] the Rasp pi before proceeding.		[[Testing/Reports/Sweets_on_Raspberry_pi_armhf_raspbian#Soft_reboot\|Soft reboot]] the Rasp pi before proceeding.

	Download the installer,		Download the installer,
Line 34:		Line 34:
	sh installer.sh		sh installer.sh

	Logout of LXDE, then {{Code\|startx}} or [[#~~Soft reboot~~\|Soft reboot]] the Rasp pi before proceeding.		Logout of LXDE, then {{Code\|startx}} or [[Testing/Reports/Sweets_on_Raspberry_pi_armhf_raspbian#Soft_reboot\|Soft reboot]] the Rasp pi before proceeding.

	You can view the sweets help file with this command.		You can view the sweets help file with this command.
Line 55:		Line 55:
	Logout of LXDE, {{Code\|startx}}, then {{Code\|sweets -h}} displays the help page correctly.		Logout of LXDE, {{Code\|startx}}, then {{Code\|sweets -h}} displays the help page correctly.


	'''Launch first sweet.''' (Launches a fairly recent version, marked "testing").		'''Launch first sweet.''' (Launches a fairly recent version, marked "testing").

Line 88:		Line 87:
	For reference, check the SD card has plenty of space: {{Code\| df -h}}. Reveals Used 2.2G, Avail 1.3G, ok		For reference, check the SD card has plenty of space: {{Code\| df -h}}. Reveals Used 2.2G, Avail 1.3G, ok

	[[#~~Soft reboot~~\|Soft reboot]]		[[Testing/Reports/Sweets_on_Raspberry_pi_armhf_raspbian#Soft_reboot\|Soft reboot]]

	Now launch again with same command		Now launch again with same command
Line 136:		Line 135:
	During testing I had unexplainable errors - possibly related Rasp pi not being able to write to certain SD cards fast enough.		During testing I had unexplainable errors - possibly related Rasp pi not being able to write to certain SD cards fast enough.

	When a reboot is needed, rather than just {{Code\|sudo reboot}} from within LXDE~~, perhaps~~, enter command {{Code\|top}} and watch while CPU activity subsides, then logout of LXDE ~~and shutdown from console~~. And/or, from the console, {{Code\|top && shutdown -r now}}. Further, after the downloads and other sections of prolonged 100% CPU activity, I have tended to use the Rpi for some light work with the idea of "settling the contents", and have an extra restart.		When a reboot is needed, rather than just {{Code\|sudo reboot}} from within LXDE. Perhaps, enter command {{Code\|top}} and watch while CPU activity subsides, then logout of LXDE. And/or, from the console, {{Code\|top && shutdown -r now}}. Further, after the downloads and other sections of prolonged 100% CPU activity, I have tended to use the Rpi for some light work with the idea of settling the contents, and have an extra restart.

	=== GUI Activity install ===		=== GUI Activity install ===

Inkyfingers: update

2012-10-06T11:05:26Z

update

Show changes

Inkyfingers: review progress

2012-07-12T13:31:35Z

review progress

← Older revision		Revision as of 09:31, 12 July 2012
Line 52:		Line 52:

	xulrunner-1.9.2		xulrunner-1.9.2

			'''Review progress'''

			So I believe I can fulfill all the dependencies of the four <sweets> options, sdk: 0.88, 0.94, and dextrose: 0.88, 0.94, so far as is revealed by:

			sweets status --deps <those four sweets>

			1. This error message keeps appearing:

			ls: cannot access /usr/lib/xulrunner-1.: No such file or directory

			''- is xulrunner fundamental to the task?''

			These are the remaining problem dependencies for -S option.

			2. error status "dr" sdk/pyabiword (0.8.0-11).

			Aptitude shows python-abiword 0.8.0-11 installed.

			3. error status "dr" sdk/hulahop (0.8.2-7)

			E: Package 'python-hulahop' has no installation candidate

			Package: python-hulahop (0.8.1-1) is shown in Debian package search as unavailable in armhf

			4. error status "dr" sdk/pyxpcom (1.9.2-15) (<2)

			Package: python-xpcom (1:9.0~hg20111212-2 and others)

			Aptitude shows python-xpcom 1:9.0~hg20111212 ''but it is out of specified range.''

			https://developer.mozilla.org/en/Building_PyXPCOM ''refers''

			5. error status "er" http://sweets.sugarlabs.org/sdk/xulrunner (>=1.9.2, <1.9.3)

			Package, squeeze: xulrunner-1.9.1 (1.9.1.16-16) [security]

			Package, sid: xulrunner-1.9.1 (1.9.1.19-2 and others)

			Package, wheezy, xulrunner-10.0 ''Is available, armhf: testing in progress''.

			''All are out of specified range.''

			https://developer.mozilla.org/en/XULRunner_1.9.2_Release_Notes ''Refers, attempted and failed to install, (i686 source)''





	'''As a known issue''' (for Debian), suggested dependencies, i.e., -S sweets command argument, don't work for now. The reason why the -S option does not work in Debian is probably fundamental to making the above process more easy to complete.		'''As a known issue''' (for Debian), suggested dependencies, i.e., -S sweets command argument, don't work for now. The reason why the -S option does not work in Debian is probably fundamental to making the above process more easy to complete.

Inkyfingers: update

2012-07-12T08:41:48Z

update

← Older revision		Revision as of 04:41, 12 July 2012
Line 1:		Line 1:
	Sugar on a Raspberry pi is functional~~, robust~~, stable, and testable unsupervised by children (in progress).		Sugar on a Raspberry pi is functional, stable, and testable unsupervised by children (in progress).

	== ~~Test report Sugar 0.94~~ ==		== Method ==
			Using a Raspberry pi, running OS from http://www.raspbian.org/ (pisces image) on a SanDisk 4 GB, class 4, SDHC card.
			The Raspian install should be fully updated as per their pages. Take care to obtain the most accurate possible configuration of locales, keyboard and sound.

	~~Product of the command~~		The Sugar via Sweets installation process instructions are here:
	~~sweets sdk/sugar~~:~~emulator~~
	~~Raspberry pi, running OS from http://www.raspbian.org/ (pisces image) on a SanDisk 4 GB, class 4, SDHC card.~~

	~~Sweets, following these instructions~~ [[Platform Team/Guide/Sugar via Sweets]]		[[Platform Team/Guide/Sugar via Sweets]]

	~~From my computer~~		and the method follows the walkthrough here:
	~~::Build: Debian GNU~~/~~Linux testing~~/~~unstable~~
	::Sugar: 0.94.1		[[Testing/Reports/Sweets on Debian Wheezy]]

			Refer to [[#Still to Fix]] and attempt to install those items straight after:

			sudo apt-get install gnome-packagekit

			'''Test report Sugar 0.94'''

	All Function keys, F1 to 6, work fine		All Function keys, F1 to 6, work fine
	All Views and avatars seen correctly, without error.		All Views and avatars seen correctly, without error.
	Software Updates fully functional. ~~These tested~~ Activities ~~fully functional.~~		Software Updates fully functional.
	~~Calculate v.40 -~~		The list of working Activities (and limitations) is very similar to those reported
	~~Chat v.77 -~~		here [[Testing/Reports/Sweets on Debian Wheezy]]
	~~Edit v.8 -~~
	~~HorseGame v.4 -~~
	~~IRC v.10 -~~
	~~Implode v.12~~
	~~Log v.29 -~~
	~~Labyrinth v.12 -~~
	~~Maze v.21 -~~
	~~Memorize v.4 -~~
	~~Moon v.14 -~~
	~~Pippy v.49 -~~
	~~Physics v.10 -~~
	~~SprayPlay v.2 -~~
	~~Sugar Commander v.8~~ -
	~~Terminal v.40 -~~
	~~Turtle Art v.149 -~~
	~~TurtleConfusion v.10.~~

	~~====~~ GUI Activity install ~~====~~
	~~Without~~ a working browser~~, we~~ can use the host browser, ~~midori~~, and pcmanfm unzip tool.		''' GUI Activity install '''

			This method is useful if a working browser is not available in Sugar. We can use the host browser, Midori, and pcmanfm unzip tool.

	Select a new Activity from ASLO, http://activities.sugarlabs.org//en-US/sugar/ . (Packages selected to run in Sugar 0.94.1 can be identified in ASLO, using "Advanced Search"). Using Midori, download chosen Activities to, say, ~/downloads. Open ~/downloads with pcmanfm, select the NewActivity.xo, right click, chose extract to, enter ~/Activities, press Save. The Activity will unzip ready to use. You can check in ~/Activities that you have NewActivity.activity		Select a new Activity from ASLO, http://activities.sugarlabs.org//en-US/sugar/ . (Packages selected to run in Sugar 0.94.1 can be identified in ASLO, using "Advanced Search"). Using Midori, download chosen Activities to, say, ~/downloads. Open ~/downloads with pcmanfm, select the NewActivity.xo, right click, chose extract to, enter ~/Activities, press Save. The Activity will unzip ready to use. You can check in ~/Activities that you have NewActivity.activity

	~~==== Fixed Items ====~~

	~~Earlier in the process, to fix:~~

	~~ImportError: No module named vte~~
	~~ImportError: No module named gst~~
	~~ImportError: No module named pygame~~

	~~sudo apt-get install python-vte python-gst0~~.~~10 python-pygame~~		==== Still to Fix ====
			The current Sweets installer does not pick up all of the dependencies first time in Debian and Raspbian.

	~~==== Still~~ to ~~Fix ====~~		The dependencies that will require manual installation are listed in the steps below.

			They are listed in order of ease. The latter items are probably more fundamental to the process. ''The best fix is still required.''

			sudo apt-get install python-vte python-gst0.10 python-pygame python-webkit

			sudo apt-get install oss-compat python-gst0.10-dev python-gst0.10-dbg timidity

	~~Issues being fixed, update shortly. [[User:Inkyfingers\|Inkyfingers]] 21:50, 11 July 2012 (EDT)~~

	~~Is there a sys~~.~~path issue? No~~		The following assets may also be required, but not yet fully resolved.

	~~Is there an issue in this area - ie change of architecture? http://docs.~~python~~.org/library/fpectl.html#limitations-and-other~~-~~considerations? No~~		python-xpcom

	~~'''As a known issue''' (for Debian), suggested dependencies, i~~.~~e., -S sweets command argument, don't work for now~~.		xulrunner-1.9.2

	~~Why does~~ -S option not work in Debian?		'''As a known issue''' (for Debian), suggested dependencies, i.e., -S sweets command argument, don't work for now. The reason why the -S option does not work in Debian is probably fundamental to making the above process more easy to complete.

Inkyfingers: prepare for update

2012-07-12T01:50:41Z

prepare for update

New page

Sugar on a Raspberry pi is functional, robust, stable, and testable unsupervised by children (in progress).

== Test report Sugar 0.94 ==

Product of the command
sweets sdk/sugar:emulator
Raspberry pi, running OS from http://www.raspbian.org/ (pisces image) on a SanDisk 4 GB, class 4, SDHC card.

Sweets, following these instructions [[Platform Team/Guide/Sugar via Sweets]]

From my computer
::Build: Debian GNU/Linux testing/unstable
::Sugar: 0.94.1

All Function keys, F1 to 6, work fine
All Views and avatars seen correctly, without error.
Software Updates fully functional. These tested Activities fully functional.
Calculate v.40 -
Chat v.77 -
Edit v.8 -
HorseGame v.4 -
IRC v.10 -
Implode v.12
Log v.29 -
Labyrinth v.12 -
Maze v.21 -
Memorize v.4 -
Moon v.14 -
Pippy v.49 -
Physics v.10 -
SprayPlay v.2 -
Sugar Commander v.8 -
Terminal v.40 -
Turtle Art v.149 -
TurtleConfusion v.10.

==== GUI Activity install ====
Without a working browser, we can use the host browser, midori, and pcmanfm unzip tool.

Select a new Activity from ASLO, http://activities.sugarlabs.org//en-US/sugar/ . (Packages selected to run in Sugar 0.94.1 can be identified in ASLO, using "Advanced Search"). Using Midori, download chosen Activities to, say, ~/downloads. Open ~/downloads with pcmanfm, select the NewActivity.xo, right click, chose extract to, enter ~/Activities, press Save. The Activity will unzip ready to use. You can check in ~/Activities that you have NewActivity.activity

==== Fixed Items ====

Earlier in the process, to fix:

ImportError: No module named vte
ImportError: No module named gst
ImportError: No module named pygame

sudo apt-get install python-vte python-gst0.10 python-pygame

==== Still to Fix ====

Issues being fixed, update shortly. [[User:Inkyfingers|Inkyfingers]] 21:50, 11 July 2012 (EDT)

Is there a sys.path issue? No

Is there an issue in this area - ie change of architecture? http://docs.python.org/library/fpectl.html#limitations-and-other-considerations? No

'''As a known issue''' (for Debian), suggested dependencies, i.e., -S sweets command argument, don't work for now.

Why does -S option not work in Debian?