On Tue, Apr 08, 2008 at 04:07:52PM -0700, Wade Berrier wrote:
I would guess that osc could automatically take care of removing that file if it needed.
There is not really a way for osc to know that it should discard its cookies. The usual way is that the server replies with a cookie that superseeds the one that the client has. If the api decides to become incompatible to itself and choke on the cookies that it gave out in the past, and replies with a "500 Internal Server Error", it is a bug there. Normally, it should answer with "401 Unauthorized", which triggers a code path in the client which makes it reauthenticate (and save the new cookie). A 500 leads to a "give up" response in the client. There is no provision to retry things if a 500 is encountered. Adrian added a workaround to osc on the weekend. It is committed to svn and to the openSUSE:Tools package. However, it would be better to fix the api, because that would also help those users that didn't update their osc package so far. (Or those that use the Factory osc package, or any other released one). Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development