Bug#601971: unblock: liboauth/0.9.1-1
On Mon, 01 Nov 2010 11:12:25 +0100, Mehdi Dogguy wrote: > > I guess this is one of the cornercases where we have to sacrifice > > an improvement in a small corner in order to improve the larger good > > (i.e. get out the release without unnecessary delays and risk for the > > quality). > What are the other clients that may use liboauth? Is bti the only one? I don't know (probably there are some), maybe Bilal knows more about this? > Liboauth was just released… how much testing did it get? With bti I've only tested that it builds (and I know that a newer bti + liboauth are in maemo5). Unless someone convices me to create a twitter account it's also a bit difficult for me to actually test it with twitter :) Oh, but identi.ca might work with OAuth too, I need to check this. I gues uploading bti to experimental might make testing for others easier ... Cheers, gregor -- .''`. http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4 : :' : Debian GNU/Linux user, admin, & developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of Free Software Foundation Europe `-BOFH excuse #194: We only support a 1200 bps connection. signature.asc Description: Digital signature
Bug#601971: unblock: liboauth/0.9.1-1
On 11/01/2010 01:21 AM, gregor herrmann wrote: > > JFTR: bti would already (build-)depend on it if it had been around > longer :) > Sure :) > (In fact I have a package ready with the new upstream release of bti > which uses liboauth). > >>> libOAuth was accepted very recently into Debian Unstable, and that >>> is why it isn't in squeeze yet. >> Then, we won't be able to accept it in Squeeze I'm afraid. > > Right, that's totally understandable. > > I guess this is one of the cornercases where we have to sacrifice > an improvement in a small corner in order to improve the larger good > (i.e. get out the release without unnecessary delays and risk for the > quality). > What are the other clients that may use liboauth? Is bti the only one? Liboauth was just released… how much testing did it get? Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601971: unblock: liboauth/0.9.1-1
On Sun, 31 Oct 2010 16:51:13 +0100, Mehdi Dogguy wrote: > > Without this package, BTI and other twitter clients will not function in > > squeeze, as they would not be able > > to authenticate with Twitter. > While this appears to be useful for Twitter clients (those actually > using the lib), there is not a single application build-depending on > this library for now. So, why should we accept this in Squeeze? JFTR: bti would already (build-)depend on it if it had been around longer :) (In fact I have a package ready with the new upstream release of bti which uses liboauth). > > libOAuth was accepted very recently into Debian Unstable, and that > > is why it isn't in squeeze yet. > Then, we won't be able to accept it in Squeeze I'm afraid. Right, that's totally understandable. I guess this is one of the cornercases where we have to sacrifice an improvement in a small corner in order to improve the larger good (i.e. get out the release without unnecessary delays and risk for the quality). (And we can then upload a newer bti + liboauth + other clients into backports.) Cheers, gregor -- .''`. http://info.comodo.priv.at/ -- GPG key IDs: 0x8649AA06, 0x00F3CFE4 : :' : Debian GNU/Linux user, admin, & developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of Free Software Foundation Europe `-BOFH excuse #244: Your cat tried to eat the mouse. signature.asc Description: Digital signature
Bug#601971: unblock: liboauth/0.9.1-1
On 0, Bilal Akhtar wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > > Please unblock package liboauth > > This package is blocking major bugs in twitter clients, an example of such a > bug is bug #588235 . > Twitter recently dropped support for Basic Auth and now all twitter clients > are forced to use OAuth to > authenticate to Twitter. libOAuth is the ONLY OAuth 1.0 library written in C, > and hence all Twitter clients > written in C need this. > > Without this package, BTI and other twitter clients will not function in > squeeze, as they would not be able > to authenticate with Twitter. > While this appears to be useful for Twitter clients (those actually using the lib), there is not a single application build-depending on this library for now. So, why should we accept this in Squeeze? > libOAuth was accepted very recently into Debian Unstable, and that > is why it isn't in squeeze yet. Then, we won't be able to accept it in Squeeze I'm afraid. Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601971: unblock: liboauth/0.9.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package liboauth This package is blocking major bugs in twitter clients, an example of such a bug is bug #588235 . Twitter recently dropped support for Basic Auth and now all twitter clients are forced to use OAuth to authenticate to Twitter. libOAuth is the ONLY OAuth 1.0 library written in C, and hence all Twitter clients written in C need this. Without this package, BTI and other twitter clients will not function in squeeze, as they would not be able to authenticate with Twitter. libOAuth was accepted very recently into Debian Unstable, and that is why it isn't in squeeze yet. unblock liboauth/0.9.1-1 -- System Information: Debian Release: squeeze/sid APT prefers maverick-updates APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 'maverick') Architecture: i386 (i686) Kernel: Linux 2.6.35-22-generic (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
