|
Bugzilla – Full Text Bug Listing |
| Summary: | Synchronizing installation sources doesn't reflect on the status change On/Off of the source | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Lukas Ocilka <locilka> |
| Component: | YaST2 | Assignee: | Martin Vidner <mvidner> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | kkaempf |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2log | ||
|
Description
Lukas Ocilka
2006-06-02 08:15:19 UTC
Created attachment 86763 [details]
y2log
When disabling/re-enabling sources, YaST probably has to call 'rug' and pass this status change to zmd. I see. I am not sure whether the Status column really means the same thing, as I cannot see a way in rug help to leave a service added but disabled. I have only seen the Pending status besides Active. Is there a way? If I understood correctly, there is a setting to make a service inactive (which one?) but in fact it only makes the service lower priority than the active ones. Originally reported on SLES10 RC2 Moving to make it public. James says that there's no such setting. We can just remove the service on inactivation and add it on activation. *** This bug has been marked as a duplicate of bug 182992 *** |