Please backport ttytter 2.1.0-1 (multiverse) from raring

[Stephen Michael Kellat]

Please backport ttytter 2.1.0-1 (multiverse) from raring to precise,
  quantal.

  Reason for the backport:
  ========================
  Versions prior to the one packaged in Raring Ringtail cannot access Twitter APIs since March 2013.

  Testing:
  ========
  Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing.

  You can test-build the backport in your PPA with backportpackage:
  $ backportpackage -u ppa:skellat/test -s raring -d precise ttytter
  $ backportpackage -u ppa:skellat/test -s raring -d quantal ttytter

  * precise:
  [X] Package builds without modification
  [X] ttytter installs cleanly and runs
  * quantal:
  [X] Package builds without modification
  [X] ttytter installs cleanly and runs

  No reverse dependencies

[Scott Kitterman (kitterman)]

Rather the update the entire package, it would be better to do a post-release update that addresses just the twitter API changes since that will benefit all users of the package an not just the ones that choose to install from backports. See:

https://wiki.ubuntu.com/StableReleaseUpdates

[Stephen Michael Kellat (skellat)]

While this is a high-impact bug, it does not necessarily appear that SRU criteria are met to patch prior versions. Other Twitter internal changes were fixed between 1.2.5, the version Precise has, and 2.1.0, which is found in Raring as well as in Sid. Upstream had to kill race conditions in multiple releases between the version in Precise and the one in Raring.

The versions of TTYtter shipped in Precise and Quantal cannot access Twitter now but due to the API changes Upstream had to do a major rewrite. It did not appear upon review that API compliance could be grafted onto the prior versions.

These are the changes logged by upstream between the versions in Precise and Raring:

 Changes in version 2.1.0:

    This version of TTYtter requires Twitter API 1.1. Twitter-alike services not compliant with API 1.1 will not work with this or any future version of TTYtter. If you need API 1.0 support, you must use 2.0.4 for as long as that support is available.

    Full compliance with Twitter API 1.1, including TOS limitations and rate limits.
    TTYtter now deshortens t.co links transparently for tweets and events, and uses t.co length computations when determining the length of a tweet. This feature can be disabled with -notco. If you are using Term::ReadLine:TTYtter 1.4 or higher, then this will also work in readline mode.
    Commands that accept menu codes can now also accept tweet or DM IDs, perfect for all you command-line jockeys.
    New /replyall command (thanks @FunnelFiasco).
    New /del command.
    User filtering (with new -filter* options).
    Better description of the full range of streaming events (thanks @RealIvanSanchez).
    /push now works with non-Boolean options, simply pushing them to the stack (it still sets Booleans to true when pushed).
    The background will kill itself off correctly if the foreground process IPC connection is severed (i.e., the console died), preventing situations where the background would panic or peg the CPU in an endless loop.
    Geolocation now looks at and processes place ID, country code, name and place type, and tweets with a place ID will also be considered to have geolocation information (thanks @RealIvanSanchez).
    Using -twarg generates a warning. As previously warned, it will be removed in 3.0.
    -anonymous now requires -apibase, as a Twitter API 1.1 requirement.
    All bug fixes from 2.0.4.

Changes in version 2.0.4 (bug fixes and critical improvements only; these fixes are also in 2.1.0):

    2.0.x will be the last branch of TTYtter to support Twitter API 1.0. When the 1.0 API is shut down, all previous versions of TTYtter will fail to work and you must upgrade to 2.1.x.

    You can now correctly /push booleans that were originally false.
    /eval now correctly emits its answer to $streamout so that -runcommand works.
    /vcheck on T::RL::T now correctly reports the currently installed version rather than the server's version when the installed version is the same or newer.
    Error messages from Twitter are properly processed again, so that commands that really fail won't unexpectedly appear to succeed.
    Hangs or spurious errors in -daemon mode are now reduced.
    T...

[Stephen Michael Kellat (skellat)]

Waiting on a Quantal ISO to download so I can test in a VM.

[Stephen Michael Kellat (skellat)]

I have tested the backport test package on Precise & Quantal and found it to run and correctly access Twitter while being able to post and access user timeline.

[Micah Gersten (micahg)]

Accepted based on testing provided, uploading

[Micah Gersten (micahg)]

I meant approved before, uploads now accepted