Joanmarie Diggs wrote:
On Tue, 2009-06-30 at 09:48 -0700, Brock Pytlik wrote:
To help determine where the problem lies, could you please try 'pkg
search gnome' and 'pkg search python' from the command line and see what
happens?
Thanks,
Brock
I'm doing 'pkg search gnome' at the moment. It's still cranking away --
my timeout is now set to 300. :-) BUT, pkg is displaying things and
started doing so almost immediately. For what it's worth, as an
end-user, the experience with the command line feels better: At least I
know it's doing *something*. With the current gui implementation, the
results list is blank for an awfully long time -- and comes up empty
without an extremely long timeout. Perhaps packagemanager could display
results along the way?
Given the timeout issue, would it make sense to add an option to the
packagemanager Preferences dialog through which users could increase the
value of PKG_CLIENT_TIMEOUT?
The other thing I'm wondering is if you all could be persuaded to
re-enable offline/local searching in packagemanager. Perhaps not by
default -- maybe it could be a setting in Preferences? Or perhaps in the
instance of a timeout, search could fall back on a local search??
At the risk of sounding nonconstructive, which I really don't want to
sound, packagemanager search used to be a useful tool to me. It's
feeling far less so with these recent changes. (Sorry!)
Thanks for the explanations and help! Take care.
--joanie
I'll admit I'm confused about why changing the timeout makes a
difference here. If you have a chance, could you put it back to its
previous value (or delete it from your environment) and try 'pkg search
gnome' and perhaps 'pkg search /usr/bin > /dev/null' on the command line
again? I'd like to figure out whether the timeout is happening because
of the search API or the packagemanager. Because the way the api works
(reading things from the server dynamically), in general it shouldn't
time out even when thousands of results are coming back. Basically,
whether or not you can reproduce the timeout behavior on the command
line will point to where we need to fix the problem.
Thanks,
Brock
jmr wrote:
Joanmarie Diggs wrote:
On Tue, 2009-06-30 at 11:21 -0500, Shawn Walker wrote:
Joanmarie Diggs wrote:
Hi guys.
I'm having "one of those days," so before I file a bug I thought
I'd ask
here for a reality check. :-)
Is search broken for anyone else but me? Beginning with revision 1179,
if I type a term in the Search entry (e.g. 'gnome') and press Return,
the result (after 30 seconds) is an empty list, a timeout
indication in
the statusbar, and a dialog indicating failure on the dev repo. If I
revert to 1178 it's all good again.
If this is not just me, I'll file the bug.
Search now requires a network connection to the repositories you
have to work as it uses the pkg(5) api to search. Before it only
did local searches and did not require a network connection by default.
What search are you trying to perform, and what is the output of:
pkg publisher
I'm searching for 'gnome' in the category All Applications.
With gnome you will get a lot of hits which might be causing the
timeout issues on the depot side, try searching for "python" say and
see how it goes. For "python" I get 52 hits against opensolaris.org
(http://pkg.opensolaris.org/release/) in 13 seconds.
JR
$ pkg publisher
PUBLISHER TYPE STATUS URI
opensolaris.org (preferred) origin online
http://pkg.opensolaris.org/dev/
contrib origin online
http://pkg.opensolaris.org/contrib/
extra origin online
https://pkg.sun.com/opensolaris/extra/
pending origin online
http://pkg.opensolaris.org/pending/
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
