Bug#601971: Please unblock
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/23/2010 01:33 PM, Mehdi Dogguy wrote:
> reopen 601971
> tags 601971 + moreinfo
> thanks
>
> On 0, Bilal Akhtar <bilalakhtar@ubuntu.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> This upload was blocked again due to
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601971 . Now, it has
>> been found that that bug is not due to liboauth (see last comment on
>> that bug about the fact that twitter OAuth works). Its a problem with
>> bti, in which bti is using identi.ca where OAuth is not needed.
>>
>> Could someone please unblock this package? The reason I want this to
>> happen early is because I want it to enter squeeze quite some time
>> before release so that we have a safe margin.
>>
>
> Is it possible for identi.ca users to still use bti? The reason to have
> liboauth in Squeeze is to allow bti to work with Twitter. But, if it
> introduces a regression (here wrt. identi.ca) then, it won't be unblocked.
LibOAuth works well with identi.ca (both of them use the same OAuth 1.0
spec) it isn't introducing a regression. The problem is with BTI, which
is using the twitter OAuth links for identi.ca . It is an easy fix,
which gregor will commit soon.
It isn't any regression or something. The library works well with
Twitter and the same case is with Identi.ca.
Bilal Akhtar.
>
> (I didn't test yet since I don't use twitter or identi.ca)
>
> Regards,
>
- --
Bilal Akhtar - Ubuntu Developer, yet still 14 years old.
More information about him can be found on
https://edge.launchpad.net/~bilalakhtar
IRC nick: bilalakhtar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJM65tmAAoJENsMxwzgYeH2UnIH/3Lyw+oGnycox+VO50ZceKRY
//3VsOxljLSd3SV7EQiPGG6nyrNHGmyGoT4RYnrZr0lqTuf3K608sGmRr9Gva7aY
viuXSbO3tnk8SfNY0nIi5Dfv/xi8L5pGt2GUciLKaYDcHzzONlbHhdwGaBFMjNly
8v9ogMIYyDoQlOEIMjUXDytgtZ/xXQwkcrl21A13PHzoCYbR+FyMT9TZI8/8yrGF
Z8hPEWvHxfiZoWgToKXPU0lZo/8EQlhE3KO/Xn3ZdaFNTs0bbpove/tNsp+xJW8t
EFE/6RahRu5r1BXLG1Up8uG7IZkSIGFAbgzFTcSDPTPECrw2540l8QMi2jAh7o8=
=LL2s
-----END PGP SIGNATURE-----
Reply to: