Changes

Jump to navigation Jump to search
Line 63: Line 63:     
=== Troubleshooting ===
 
=== Troubleshooting ===
 +
 +
After getting any unpredictable Sweets behaviour, read the following notes.
 +
 +
'''Keep feeds up-to-date'''
    
''Feeds'' are being updated from time to time. After experiencing any problems, and for refreshing the local ''feeds'' cache, it will be useful to re-download ''feeds''. Use, once, the {{Code|-R}} command line argument for the launch command (make sure that {{Code|-R}} goes before the {{Code|SWEET}}, because using it afterwards will cause passing it as a {{Code|SWEET}}'s argument):
 
''Feeds'' are being updated from time to time. After experiencing any problems, and for refreshing the local ''feeds'' cache, it will be useful to re-download ''feeds''. Use, once, the {{Code|-R}} command line argument for the launch command (make sure that {{Code|-R}} goes before the {{Code|SWEET}}, because using it afterwards will cause passing it as a {{Code|SWEET}}'s argument):
    
  sweets -R SWEET
 
  sweets -R SWEET
 +
 +
'''Analyze dependencies tree'''
    
If {{Code|sweets}} can't find a proper ''implementation'', see the {{Code|e}} lines in the output of:
 
If {{Code|sweets}} can't find a proper ''implementation'', see the {{Code|e}} lines in the output of:
    
  sweets status SWEET -vdd
 
  sweets status SWEET -vdd
 +
 +
'''Keep the system in consistent state'''
    
Asking Sweets to launch a sweets might mean installing new packages via PackageKit. In most cases, PackageKit can handle possible issues with native packages and, at worst, will fail as well, in order to stop any further Sweets operations. Nevertheless, it can be useful to keep unbroken native packages.
 
Asking Sweets to launch a sweets might mean installing new packages via PackageKit. In most cases, PackageKit can handle possible issues with native packages and, at worst, will fail as well, in order to stop any further Sweets operations. Nevertheless, it can be useful to keep unbroken native packages.

Navigation menu