Hi again Sebastian, in conversation with mvo he feels and I agree that we'd prefer not to make this change so close to release after all. For one thing, it seems like with a bit more time and in consultation with you we may be able to provide a more generally useful capability in aptdaemon than the current "remove_sources" as it stands, which implements what is really a very narrow use case for a feature in Software Center that will probably be used very rarely anyway (deauthorizing a computer for purchases). In addition, this change would require a string freeze exception for the status update strings for from aptdaemon, and it's quite late for that.
With the deauthorize feature as it currently stands in Software Center, the Ubuntu SSO credentials are removed and all purchased software is uninstalled, and this meets the requirements of the spec. The clearing of the sources.list is just needed to remove all trace of the purchased repositories themselves, but again, since this will very likely be a rarely used feature it's not a big problem that we don't remove them for now. Certainly it doesn't justify the risk of changing these two packages at this stage in the cycle. Therefore, I have retargeted this bug for natty-updates and we can consider this for an SRU. We will also want to add a target for Oneiric so we can track it there as well. Meanwhile, let's have a conversation, perhaps at UDS if I will see you there, about what kind of implementation would have the most benefit for aptdaemon. Thanks again! Gary -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/723911 Title: deauthorize does not remove sources.list -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
