Source: bitlbee Version: 1.2.8-1 Severity: normal Tags: upstream fixed-upstream Control: fixed -1 3.2-1
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 If I'm understanding the situation correctly, 3.2 has added support for Twitter's API version 1.1, so versions before this will start to fail in their attempts to connect to Twitter at some point in the future. Cf. https://dev.twitter.com/blog/planning-for-api-v1-retirement Since BitlBee has many more functions (and I don't use Twitter anyway :)), I'm setting the severity to 'normal', others might disagree ... Cheers, gregor -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRPjxTAAoJELs6aAGGSaoGlFoQAIDWJcyhDlSVHy0+yw0b8oCV fd1i5Mp1NbkRc3IEEG7FAqZywrqQz46DkdFSEsTSwfbuIJLMs93nMRZYaRa5JvmS yQRhOh94VnV1Oy5g1AltJ9zH0B9Wnv8S6XqFqMvr58ZbOSuC3spGGo0Vg6II6taF wKkx0ISzfH0jHEv/AK+28UZDTNuS7fssDzRd0iNQBKrQ4Zdp3pLQU5CpIVGBqvz/ ui2En79gwbVAON0tNxD5IQd1czt85fOJ7ldQhKHg5EPtakFHqCHFfpTF3KoiPVcz Em//3/7RG2Qa4wJkrz5DKHveaKqQb4LbOYI9En1jAoEeuK+OxAhtj4nxwqsX6854 qPWS5OVK3Mi0aB0JRt+P/m0V/l2gKVyq0lqQqu9loF5kCdT7kCD5+RJ/fJLfoEv7 XwbHE2HBbPrlrc5eFBofiqEZcJGRZu4rANmhccjqgyEPbFztTfLcDDv740pgVh1Q aHXohKRVd/+83rb6Ny0HtYT60Dt4ubgDzjVF0KhUvpMrsvhlhT58c/sDWeKEzxJo HosLE6WQohG+V3ViMh0fN+YMeI7PfU5OEkqfouH1kqowzp2CRKvLdPLNn+T4gGG2 X4o1I9q+w+8cJXFp3O8rvkDtoRrwSoty9o/xRF+bVJ6HT+2niVweu01t0Won8tVy TpdDcw6uaVS97y0jLSxb =VIc2 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
