Hi Stephen, On Fri, December 28, 2012 22:15, Stephen Michael Kellat wrote: > 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.
The new TTYtter 2.1.0 release is as of now available in Debian unstable. I have considered the options for this bug. I find that option 1 seems highly unlikely since it indeed means to allow a freeze exception for not only a new upstream release but a complete upstream new branch (2.1 vs 2.0). Besides that the package also requires upgrading Term::Readline::TTYtter to 1.4. I believe we best discount this option. Option two is certainly at our disposal. I doubt however that we should ask for removal from wheezy. Firstly, because it still works now, and we can always pull it from wheezy later when the API indeed is discontinued. And secondly, because TTYtter may still be useful for non-Twitter usage. Most notably identi.ca, which is used extensively in the free software world. So I'm inclined to go for the following path: a. Fix the problem in unstable. That has now been done. b. Lower this bug to severity 'important', to not require removal of TTYtter from Wheezy now or in the future. c. Invest effort to ensure that a version that supports Twitter is available for Wheezy. This can be done after release via Debian Backports or via the Stable Updates suite. If we change our mind on the 'b' step, we can always ask for removal later, we do not lose that option. Cheers, Thijs -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
