Please unblock twidge

2010-10-25 Thread John Goerzen

Release folks,

twidge 1.0.6 was just accepted into unstable.

Twitter revoked [1] twidge's API keys (a pig-headed move, but there it 
is.)  This means that twidge is broken by default.


I made a new version that uses new API keys, and prevents them from 
showing up in the source in the clear.  This is a minimally invasive 
patch designed to meet the requirements for squeeze, and is at [2]. 
Please laugh at the obfuscation algorithm if you wish.  This appears to 
be what they want (found out by trial and error by others).


There was also a small fix [3] to the manpage for users of identi.ca. 
No other changes.


Thanks,

-- John Goerzen

[1] http://github.com/jgoerzen/twidge/wiki/FrequentlyAskedQuestions

[2] 
http://github.com/jgoerzen/twidge/commit/9421da8999efb3322e86c30f8f026af3529576e3


[3] 
http://github.com/jgoerzen/twidge/commit/d5e6e32fdac5adb367b7e2f4250f58d1d1d27003



--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cc643f1.8050...@complete.org



Re: Please unblock twidge

2010-10-25 Thread John Goerzen

On 10/25/2010 09:58 PM, John Goerzen wrote:

Release folks,

twidge 1.0.6 was just accepted into unstable.


I should have added that it fixes grave bug #601427, which complains of 
this issue.


-- John


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cc64415.5000...@complete.org