Meego Wiki
Views

Distribution/Package Management

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
(Created page with "MeeGo Package Management")
Line 1: Line 1:
MeeGo Package Management
MeeGo Package Management
 +
 +
 +
==How to report a bug==
 +
===PackageKit or Package Manager UI bug===
 +
For Package Management component issue, please catch more logs and attach them when you reporting a bug.
 +
For PackageKit or Package Manager UI issue
 +
Steps to get logs:
 +
* Setup system Environment
 +
* Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
 +
* start packagekitd manually. In one terminal execute:
 +
    #killall -9 packagekitd
 +
    #/usr/libexec/packagekitd -v >packagekitd.log
 +
* In another terminal execute your script/command to reproduce bug.
 +
* Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time.    Please attach them.
 +
===zypper command bug===
 +
For Zypper issue while you using zypper command, using the following steps to get logs:
 +
* Setup system Environment
 +
  #rm /var/log/zypper.log -f
 +
* set log level and reproduce bug using zypper
 +
    #export ZYPP_LIBSAT_FULLLOG=1
 +
    #zypper xxx yyy
 +
or using the following log level
 +
    #export ZYPP_FULLLOG=1
 +
    #zypper xxx yyy
 +
* check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).

Revision as of 01:58, 1 July 2011

MeeGo Package Management


How to report a bug

PackageKit or Package Manager UI bug

For Package Management component issue, please catch more logs and attach them when you reporting a bug. For PackageKit or Package Manager UI issue Steps to get logs:

  • Setup system Environment
  • Install PackageKit-debuginfo, libzypp-debuginfo, which should match the version of PackageKit/libzypp
  • start packagekitd manually. In one terminal execute: 
   #killall -9 packagekitd
   #/usr/libexec/packagekitd -v >packagekitd.log
  • In another terminal execute your script/command to reproduce bug.
  • Then you'll get packagekitd.log and /var/log/pk_backend_zypp, and these two log files are very important to fix bug in the first time. Please attach them.

zypper command bug

For Zypper issue while you using zypper command, using the following steps to get logs:

  • Setup system Environment 
  #rm /var/log/zypper.log -f
  • set log level and reproduce bug using zypper 
   #export ZYPP_LIBSAT_FULLLOG=1
   #zypper xxx yyy

or using the following log level 

   #export ZYPP_FULLLOG=1
   #zypper xxx yyy
  • check /var/log/zypper.log and attach them. The log generated using ZYPP_LIBSAT_FULLLOG would be very large(40M), but includde more information about packages. while the log generated using ZYPP_FULLLOG is smaller (1M).
Retrieved from "http://wiki.meego.com/Distribution/Package_Management"
Personal tools