Changes

This article does not challenge nor assume that "gnome-packagekit relies on gnome for full functionality."
Line 1: Line 1: −
These tests were carried out on an HP-dx5150 running Debian testing Wheezy amd64 version, with x-display manager, Slim, and Openbox desktop environment.
+
These tests were carried out on an HP-dx5150 desktop PC, running Debian testing Wheezy amd64 version, with x-display manager, Slim, and Openbox desktop environment. During these tests aptitude shows no missing dependencies.
   −
Following instructions here: [[Platform Team/Guide/Sugar via Sweets]]
+
'''Limitation of article'''
 +
 
 +
In Debian testing, {{Code|gnome}} is not marked as a dependency of {{Code|gnome-packagekit}}. This article does not challenge nor assume that "{{Code|gnome-packagekit}} relies on {{Code|gnome}} for full functionality."
 +
 
 +
'''[[Platform Team/Guide/Sugar via Sweets]]''' provides the instructions followed.
    
  sudo apt-get update && sudo apt-get dist-upgrade
 
  sudo apt-get update && sudo apt-get dist-upgrade
Line 10: Line 14:     
'''Restart the machine before proceeding'''
 
'''Restart the machine before proceeding'''
 +
 +
In the text that follows, the first line in the code box is the command entered, followed by the response generated.
    
  wget http://download.sugarlabs.org/sweets/sweets/installer.sh
 
  wget http://download.sugarlabs.org/sweets/sweets/installer.sh
Line 33: Line 39:  
'''Restart the machine before proceeding'''
 
'''Restart the machine before proceeding'''
   −
This is not necessary to do, but if we ran the "status of dependencies" command right now, the first lines, and last lines of response look like this:
+
It is not necessary to do this, but if we ran the "status of dependencies" command right now, the first lines, and last lines of response look like this:
    
  sweets status --deps dextrose/sugar:emulator                     
 
  sweets status --deps dextrose/sugar:emulator                     
Line 42: Line 48:  
  -- Legend: (-)ok (m)ake (d)ownload (i)nstall (e)rror (r)untime (b)uildtime (bold)local
 
  -- Legend: (-)ok (m)ake (d)ownload (i)nstall (e)rror (r)untime (b)uildtime (bold)local
   −
This tells us (and confirms) dextrose/sugar still requires to be downloaded - "dr", and libwnck-python and xephyr still require to be installed - "ir".
+
This reports (confirming known) that dextrose/sugar still requires to be downloaded - "dr", and libwnck-python and xephyr still require to be installed - "ir".
 +
 
 +
Ready to launch first sweet.
    
  sweets dextrose/sugar:emulator
 
  sweets dextrose/sugar:emulator
Line 82: Line 90:  
  ...
 
  ...
   −
This command has opened Sugar in an emulator for me, but it is not useable on my machine. No Actiities are visible in F3 Home view, and no avatars are visible in F1 neighborhood view. There is no ~/Activities folder or contents. Clicking on my avatar => My Settings => Software update, reports updates are available, but offers no means to install them.
+
This command has opened Sugar in an emulator for me, but it is not useable on my machine. No Actiities are visible in F3 Home view, and no avatars are visible in F1 neighborhood view. There is no ~/Activities folder or contents. Clicking on the central avatar (represents the user) => My Settings => Software update, reports updates are available, but offers no means to install them.
    
To find out if all dependencies are now fulfilled, run the "status, dependencies" command.
 
To find out if all dependencies are now fulfilled, run the "status, dependencies" command.
Line 133: Line 141:  
Look at first character of each line, all "-" compare with legend: "(-) = ok".
 
Look at first character of each line, all "-" compare with legend: "(-) = ok".
   −
So all dependencies have been fulfilled by Sweets. We will try a different sweet.
+
So all dependencies are reported to have been fulfilled by Sweets.
 +
 
 +
Launch a different sweet.
    
  sweets dextrose/sugar:emulator
 
  sweets dextrose/sugar:emulator
Line 154: Line 164:  
  Errors from xkbcomp are not fatal to the X server
 
  Errors from xkbcomp are not fatal to the X server
 
 
This produced a Sugar window. Clicking on my avatar => My Settings => Software update, reports updates are available. Select eight random activities, and click Install selected. Turn to the F3 Home view. Favorites view is empty, look in List view, Activities are there but nothing starts.
+
This produced a Sugar window. Clicking on central avatar => My Settings => Software update, reports updates are available.
 +
 
 +
Make a selection of these six Activities:
 +
 
 +
Chat, IRC, Labyrinth, Log, Pippy, Terminal, and click Install selected. Turn to the F3 Home view. Favorites view is empty, look in List view, Activities are there but nothing starts.
   −
Restart the machine. We will try a different sweet.  
+
Restart the machine. Launch a different sweet.  
    
  sweets dextrose/sugar:emulator = 0.94
 
  sweets dextrose/sugar:emulator = 0.94
Line 173: Line 187:  
  Errors from xkbcomp are not fatal to the X server
 
  Errors from xkbcomp are not fatal to the X server
   −
One or two items start:
+
One or two items start.
   −
After a few open the Activity Log. Look for a line for each Activity you have used in the session, the last line of the log file is what I quote here.
+
Open the Activity Log. Look for a line for each Activity you have used in the session, the last line of the log file is what I quote here.
    
spirolaterals says "no module named pygame", memorise and speak say no module named gst, MeasureActivity no module named pygst, Browse no module named hulahop.  
 
spirolaterals says "no module named pygame", memorise and speak say no module named gst, MeasureActivity no module named pygst, Browse no module named hulahop.  
687

edits