https://bugzilla.novell.com/show_bug.cgi?id=229162 Summary: rug's 'subscribed' status is confusing Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Zenworks AssignedTo: zlm-code10-bugs@forge.provo.novell.com ReportedBy: seth.arnold@novell.com QAContact: sarifulla@novell.com 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 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.