Bug 229162

Summary:	rug's 'subscribed' status is confusing
Product:	[openSUSE] openSUSE 10.2	Reporter:	Seth R Arnold <seth.arnold>
Component:	Zenworks	Assignee:	E-mail List <zlm-code10-bugs>
Status:	RESOLVED INVALID	QA Contact:	Forgotten User YrvzK78Vmi <forgotten_YrvzK78Vmi>
Severity:	Normal
Priority:	P5 - None	CC:	rashmiranjan.mohanty
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Seth R Arnold 2006-12-16 00:35:21 UTC

Why doesn't rug automatically 'subscribe' to new channels?
Why do some rug commands respect 'subscribe' but some commands don't?

When I configured a buildservice repo, but not yet subscribed, "rug info ion" wouldn't return any information about the ion package. BUT, "rug search ion" would return information about it no problem. This was very confusing.

Why do some commands respect the 'subscribed' status, and some commands not respect the 'subscribed' status? The division seemed arbitrary (not to mention the whole feature of 'subscribed' seemed arbitrary and awkward to me, but I can only assume it was added to close a bug somewhere else. But the default of not-subscribed is the most confusing thing yet. :)

Thanks

Comment 1 Rashmi Ranjan Mohanty 2007-11-23 06:36:42 UTC

Zenworks is no more part of opensuse.....

In SLE10 SP1 'rug info <pkgname>' displays
ERROR: Unable to find package '<pkgname>' in any subscribed catalog.

So the message is clear. 
Now for 'rug se' in my opinion it should search all the catalogs so that the user knows where is the package. Then if the catalog is not subscribed, then subscribe it.

So its working as expected at least in SP1. So marking this as invalid.