Luke Macken wrote: > Excerpts from Neal Becker's message of Fri May 20 07:40:41 -0400 2011: >> 3083146 build (dist-f14-updates-candidate, >> /uncrustify:6a8dd0eea2183240177154f27c10a730f20994eb) completed successfully >> Creating a new update for uncrustify-0.58-1.fc14 >> ServerError(https://admin.fedoraproject.org/updates/save, 200, Error returned >> from json module while processing >> https://admin.fedoraproject.org/updates/save: No JSON object could be >> decoded: line 1 column 0 (char 0)) Traceback (most recent call last): >> File "/usr/bin/bodhi", line 201, in main >> data = bodhi.save(**extra_args) >> File "/usr/lib/python2.7/site-packages/fedora/client/bodhi.py", line 111, >> in >> save >> 'bugs': bugs, >> File "/usr/lib/python2.7/site-packages/fedora/client/baseclient.py", line >> 344, >> in send_request >> auth_params=auth_params, retries=retries) >> File "/usr/lib/python2.7/site-packages/fedora/client/proxyclient.py", line >> 427, in send_request >> {'url': to_bytes(url), 'err': to_bytes(e)}) >> ServerError: ServerError(https://admin.fedoraproject.org/updates/save, 200, >> Error returned from json module while processing >> https://admin.fedoraproject.org/updates/save: No JSON object could be >> decoded: line 1 column 0 (char 0)) > > I'm seeing the POST requests in logs, but they're not hitting bodhi's > controller. This usually happens when the account system is having > issues, or when an exception is tossed in the identity layer of bodhi. > I believe there is already an upstream ticket to handle this better. > > Try doing `rm ~/.fedora/.fedora_session` then resubmit your update. > > luke Actually, I just tried again after changing nothing and it worked. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
