Mailinglist Archive: opensuse-bugs (4760 mails)

< Previous Next >
[Bug 597772] New: “Find” function in gpk-application is limited to accurate match
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 19 Apr 2010 13:32:32 +0000
  • Message-id: <bug-597772-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>
http://bugzilla.novell.com/show_bug.cgi?id=597772

http://bugzilla.novell.com/show_bug.cgi?id=597772#c0


Summary: “Find” function in gpk-application is limited to
accurate match
Classification: openSUSE
Product: openSUSE 11.3
Version: Factory
Platform: x86
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: libzypp
AssignedTo: zypp-maintainers@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: peter.j.zhu@xxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Blocker: ---


Created an attachment (id=355284)
--> (http://bugzilla.novell.com/attachment.cgi?id=355284)
log info of pk zypp backend

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-CN; rv:1.9.2.3)
Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729)

The Find” function in gpk-application is limited to accurate match, it means we
need to fill the full package name for search, the behavior seems incompatible
with the upstream gnome-packagekit.

In upstream gnome-packagekit project using yum backend, the “find” function
defined like this:
“You can select to search for a string that is contained in package name, the
package description, or search for the name of a file contained in the
package”.

Reproducible: Always

Steps to Reproduce:
(1)open gpk-application.
(2)find one package using “find” function. Such as "vim-common"
(3)it can find the package if using keyword "vim-common"
(3)it cannot find the package if using keyword "vim"


Expected Results:
Can search one package by using a string that is contained in package name, the
package description, or search for the name of a file contained in the package.

I attached log info here.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
< Previous Next >