Distribution/Package Management

Revision as of 02:09, 1 July 2011 (view source) Xiaoqiang0 (Talk | contribs) ← Older edit		Revision as of 15:43, 1 July 2011 (view source) Xiaoqiang0 (Talk | contribs) Newer edit →
Line 1:		Line 1:
		+	All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.
		+	==zypper==
		+	===package && pattern && patch ===
		+	=== Search Packages===
		+	zypper search --help
		+	===List Packages===
		+	zypper search
		+	===Display Package Information===
		+	zypper
		+	===Installing Packages===
		+	zypper install pkgname
		+	===Removing Packages===
		+	zypper remove pkgname
		+
		+	==PackageKit==
		+
	== How to report a bug ==		== How to report a bug ==
	=== PackageKit or Package Manager UI bug ===		=== PackageKit or Package Manager UI bug ===

---

Revision as of 15:43, 1 July 2011

All software on a MeeGo is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages using both zypper and the PackageKit suite of graphical package management tools.

Contents 1 zypper 1.1 package && pattern && patch 1.2 Search Packages 1.3 List Packages 1.4 Display Package Information 1.5 Installing Packages 1.6 Removing Packages 2 PackageKit 3 How to report a bug 3.1 PackageKit or Package Manager UI bug 3.2 zypper command bug

zypper

package && pattern && patch

Search Packages

 zypper search --help

List Packages

 zypper search

Display Package Information

 zypper 

Installing Packages

 zypper install pkgname

Removing Packages

 zypper remove pkgname

PackageKit

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).