Okay. Cameron released TTYtter 2.1.0 as of 27 December 2012 which complies with Twitter API 1.1.[1] Twitter notes on their calendar that the "drop dead" date for Twitter API 1.0 is 5 March 2013.[2] Cameron notes that all previous versions of TTYtter will cease to work with Twitter as of that date due to Twitter's API deprecation. Also noted is that Term::ReadLine::TTYtter, which currently is packaged with the script in Debian, would have to be bumped up to a new version as the currently packaged version will not play nice with the new version of the script.
The new upstream is done and Wheezy remains in freeze. The questions now: 1. Will the Release Team grant an exception since Twitter announced the major shift in API through an API deprecation on 16 August 2012 after the freeze kicked off on 30 June 2012? 2. If the Release Team will not grant an exception, can the package be pulled from shipping with Wheezy since it will likely be unusable shortly after Wheezy being released in 2013? 3. Do we have any idea if the other Twitter clients that are in the package archive are going to be ready for this API deprecation or will other packages be encountering issues if we ship them? This would be something more for the Release Team to consider than for the current bug. [1]: (http://www.floodgap.com/software/ttytter/dl.html) [2]: (https://dev.twitter.com/calendar) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
