On 04-11-15 19:34, Sebastiaan Couwenberg wrote:
> On 04-11-15 19:25, Yuri D'Elia wrote:
>> On 04/11/15 19:12, Sebastiaan Couwenberg wrote:
>>>> Some hints on what could trigger this?
>>> You may get some hints from the JOSM debug output, start josm with
>>> --debug and redirect the output to a log file:
>>>  josm --debug > /tmp/josm.log 2>&1
>> I do not see anything more related to the backtrace.
>>> Do you use the save password feature in JOSM perhaps?
>> I use OAuth. Both access key and secret are set and stored in the
>> preferences.
>> I always did (it's not something I changed recently).
> And it's not something I've used ever. That explains the difference
> between our JOSM uploads.
>>> Or by moving your ~/.josm directory out of the way, e.g. by renaming it
>>> to ~/.josm.bak, and starting with an empty profile.
>> I just tried now with regular username/password (stored in the prefs,
>> anyway), and it works. I could successfully upload a new changeset.
> I'll re-instate commons-codec in the classpath for the JOSM builds, and
> upload it to experimental for you to test.

josm (0.0.svn8969+dfsg-3~exp1) was just accepted into experimental,
please test this revision if it fixes your OAuth issue after its hits
the mirrors.

Kind Regards,


 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Pkg-grass-devel mailing list

Reply via email to