[Bug 1173817] Re: Please backport ttytter 2.1.0-1 (multiverse) from raring

Sun Apr 28 17:47:34 UTC 2013

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.
    The list_created event is now properly recognized in streaming mode.
    /entities on a retweet now properly refers back to the retweet.

Changes in version 2.0.3:

    Various and sundry Unicode whitespace characters are now canonicalized into regular whitespace, which improves URL recognition and editing. This occurs whether -seven is on or not. (thanks @Ryuutei for the report)
    You can now turn the ability of a user to send NewRTs on and off with /rtson and /rtsoff, respectively, as a down payment on full filtering in 2.1. Note that this does not currently filter NewRTs out of the stream; this is a Twitter bug.
    The user_update event is now properly recognized in streaming mode.

Changes in version 2.0.2:

    /trends now accepts WOEID (either set with /set woeid or as an argument). If none is given, global trends are used instead (WOEID 1). The old $trendurl will be removed in 2.1, since this makes it superfluous. Speak now if this affects you.
    If you have a location set with /set lat and /set long, the new /woeids command will give you the top 10 locations Twitter supports that match it. You can then feed this to /trends, or set it yourself.
    Repairs another race condition where posting before signal handlers were ready could crash TTYtter (thanks @RealIvanSanchez for the report).
    The /entities command is now smarter about media URLs.
    The exponential backoff is now correctly implemented for reconnecting to the streaming API. If a connection fails, the timeout will automatically extend to a maximum of 60 seconds between attempts. In the meantime, TTYtter will transparently fall back on the REST API.
    Extension load failure messages are now more helpful (thanks @vlb for the patch).
    Prompts were supposed to be case-insensitive, and now they are (thanks @FunnelFiasco for the patch).
    /whois (and /wagain) and /trends now correctly emit to $streamout so that -runcommand works. 

Changes in version 2.0.1:

    Expands UTF-8 support to understand UTF-16 surrogate pairs from supra-BMP code points, fixing the Malformed UTF-8 errors generated by Perl for certain characters.
    A race condition where TTYtter could accidentally kill the foreground in streaming mode is fixed (thanks @WofFS for the report).
    -backload=0 now properly populates $last_id, even if no tweets are received after the initial "fetch," eliminating an issue with spuriously grabbing old tweets (thanks @Duncan_Rowland for the report).

Changes in version 2.0.0:

    Introduces Streaming API support (opt-in) on systems satisfying prerequisites, using Twitter User Streams.
    Reworked event and select() handling for better reliability on a wider array of operating systems.
    List methods are now overhauled to remove deprecated endpoints. As a consequence, if your extension relied on the undocumented function &liurltourl, you must update it, as that function is no longer used for the current REST API revision.
    The old public_timeline endpoint is deprecated by Twitter and has been removed. Anonymous users will only see tracked terms, if any.
    /tron, /troff and /track are now case-insensitive, matching the Search API (thanks @_sequoia for the report).
    $conclude is now properly called after /again.
    Now that Twitter properly supports retweet counts greater than 100, so does TTYtter.
    Underlining of user names properly ignores hyphens.
    TTYtter will no longer run with Term::ReadLine::TTYtter versions prior to 1.3.
    Various cosmetic fixes.
    API changes: $eventhandle for receiving non-tweet/DM events from the Streaming API.
    -twarg, a very old holdover of the old single-extension API in TTYtter 0.x, is now deprecated; it does not scale in the multi-module environment. It will be removed in 3.0. Migrate your extensions now.
    -oldstatus, which was deprecated in 1.1.x, is now removed. If you are relying on the old behaviour, you must use 1.2.5.
    xAuth (not XAuth), which was deprecated in 1.2.x, is now removed. If you are relying on the old little-xAuth authentication system, you must use 1.2.5. 

** Description changed:

  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:
- [ ] Package builds without modification
+ [X] Package builds without modification
  [ ] ttytter installs cleanly and runs
  * quantal:
- [ ] Package builds without modification
+ [X] Package builds without modification
  [ ] ttytter installs cleanly and runs

  No reverse dependencies

-- 
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Precise Backports.
https://bugs.launchpad.net/bugs/1173817

Title:
  Please backport ttytter 2.1.0-1 (multiverse) from raring

To manage notifications about this bug go to:
https://bugs.launchpad.net/precise-backports/+bug/1173817/+subscriptions