Control: tag -1 wheezy Hi, Thijs Kinkhorst <thijs@debian.org> (2013-09-05): > I'd like to see the possibilities of updating TTYtter in stable. The > goal is to make TTYtter work with the new Twitter API: the version > currently in wheezy is unusable because of this API change. > > As the API change was very significant, in my opinion the only > feasible way to solve it, would be to import the "new" upstream > release that fixes that. > > To the defense of this proposal: the new upstream release has been out > since December 2012, no bug fix releases have been necessary since > then and it has been in unstable since that time aswell, so I reckon > the chances of breakage are small. > > Attached is what the debdiff would look like (if some ftpmaster magic > is possible to place the version currently in jessie in wheezy, then > that would achieve the same thing). if the idea is rebuilding 2.1.0-1 in wheezy, you probably could, or even should version it as 2.1.0-1~deb7u1 (adding a changelog entry on top of what's in unstable/testing). > Please let me know if this is acceptable. The alternative is that the > package is removed and we provide this version via backports. The idea doesn't look crazy to me, but the diff is huge… I think I might wait for another opinion on this one. Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature