You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
(264) |
May
(184) |
Jun
(34) |
Jul
(41) |
Aug
(13) |
Sep
(47) |
Oct
(48) |
Nov
(19) |
Dec
(17) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(37) |
Feb
(6) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
(21) |
Feb
(28) |
Mar
(15) |
Apr
(56) |
May
(11) |
Jun
(6) |
Jul
(22) |
Aug
(41) |
Sep
|
Oct
(30) |
Nov
(6) |
Dec
(8) |
2008 |
Jan
|
Feb
(1) |
Mar
(5) |
Apr
|
May
(4) |
Jun
(35) |
Jul
(21) |
Aug
(22) |
Sep
|
Oct
(21) |
Nov
(36) |
Dec
|
2009 |
Jan
|
Feb
|
Mar
(7) |
Apr
(3) |
May
(10) |
Jun
(1) |
Jul
(20) |
Aug
(29) |
Sep
(21) |
Oct
(14) |
Nov
(23) |
Dec
(5) |
2010 |
Jan
|
Feb
(6) |
Mar
(2) |
Apr
(16) |
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
From: Siddhesh P. <sid...@gm...> - 2010-12-28 10:54:02
|
On Tue, Dec 28, 2010 at 2:26 PM, Philip Tellis <phi...@gm...> wrote: > could someone update the article link on this page > http://ayttm.sourceforge.net/links.php to point to here: > http://www.expresscomputeronline.com/20030602/indcomp1.shtml Done. -- Siddhesh Poyarekar http://siddhesh.in |
From: Philip T. <phi...@gm...> - 2010-12-28 08:56:30
|
could someone update the article link on this page http://ayttm.sourceforge.net/links.php to point to here: http://www.expresscomputeronline.com/20030602/indcomp1.shtml they switched from php to shtml -- hello world |
From: Siddhesh P. <sid...@gm...> - 2010-10-03 10:49:41
|
Hi, I have committed a New Preferences window I have been working on, hoping to make it a little easier to use. Here is a summary of changes in behaviour: - Accounts and plugin lists are now lists - Smileys come under Chat - Got rid of the "Misc" option. Everyting is now in "Advanced" - Got rid of the OK/Cancel buttons. Save preferences on the fly - Use font button, file chooser buttons wherever appropriate - Trimmed prefs.c accordingly Apart from this, I have removed the smiley previews for now. I am trying to think of a way to show preview of only one smiley theme at a time, using a drop down selection. I am having trouble keeping it backward compatible, so any ideas are welcome. Any feedback regarding changes to this are welcome. -- Siddhesh Poyarekar http://siddhesh.in |
From: Siddhesh P. <sid...@gm...> - 2010-07-10 20:51:11
|
Hi, Sorry for the lack of a heads-up before I did this. I had a little bit of time today and I thought I could quickly release fixes that have gone in so far. Following is a summary of the changes: * Yahoo support is now based on the libyahoo2 library. It always was, but earlier we had a copy of libyahoo2 in the source tree. Not anymore. * Fixes to spell check code * Some code clean up in the module loading section The complete ChangeLog is available here: http://ayttm.git.sourceforge.net/git/gitweb.cgi?p=ayttm/ayttm;a=blob_plain;f=ChangeLog;hb=AYTTM_0_6_3 For packagers, an additional dependency will be required for ayttm now, which is libyahoo2 >= 1.0.0. -- Siddhesh Poyarekar http://siddhesh.in |
From: Siddhesh P. <sid...@gm...> - 2010-05-29 09:20:59
|
Hi, The last commit to ayttm removes the libyahoo2 copy in ayttm from the build tree (not from the repository) and instead, dynamically links against the libyahoo2 library. So packagers will have to modify their build specific dependency list to include libyahoo2. The code base has always been in sync and it has usually been a bit of a headache to do so due to having to make the same changes twice. That is no longer the case now. There are some promising plans for the libyahoo2 project, with two students proposing[1,2] improvements to libyahoo2 as part of the Fedora Summer Coding[3] event. Hopefully this will bring back the yahoo protocol support back on track. [1] https://fedoraproject.org/wiki/Summer_Coding_2010_proposal_-_web_cam_support_implementation_in_libyahoo2 [2] https://fedoraproject.org/wiki/Summer_Coding_2010_proposal_-_libyahoo2_chatroom [3] https://fedoraproject.org/wiki/Summer_Coding_2010 -- Siddhesh Poyarekar http://siddhesh.in |
From: 2134918 <21...@gm...> - 2010-04-20 19:07:18
|
If you download sources from git repo, you'll need to run ./gen before ./configure. You will also need to install following packages, if you don't have them yet: yum install flex yum install bison yum install libtool* yum install enchant* yum install libXpm-devel yum install gettext plus packages mentioned on http://ayttm.sourceforge.net/dev.php Now interesting thing: the configure script from tar.gz file didn't say anything about gettext - even without it I was able to run make and compile it (but then crashed...). Only ./gen was able to warn me about lack of gettext. |
From: Philip T. <phi...@gm...> - 2010-04-20 18:12:32
|
On 20 April 2010 08:15, Aniket Suryavanshi <ki...@gm...> wrote: > >> [root@globex ayttm-0.6.2]# ./configure >> checking for a BSD-compatible install... /usr/bin/install -c Hi Aniket, You really shouldn't be running configure as root. Run the configure and make commands in your own account, and only use root (better would be sudo) to do the make install step. Philip PS: If you want to start development, then you'll be better off getting the code from git. |
From: Aniket S. <ki...@gm...> - 2010-04-20 15:33:23
|
On Tue, Apr 20, 2010 at 8:50 PM, Siddhesh Poyarekar < sid...@gm...> wrote: > > > It says that you don;t have libtool libraries. You need to install > libtool-ltdl-devel. > > > -- > Siddhesh Poyarekar > http://siddhesh.in > > Hi Siddhesh, I'll get it fixed. Will email again when it's done or having any problems. Thanks. Regards, Aniket. -- Aniket Suryavanshi B.Sc. (Computer Science) student, India. aniket.wordpress.com twitter.com/kietan www.facebook.com/aniket1 |
From: Siddhesh P. <sid...@gm...> - 2010-04-20 15:20:11
|
On Tue, Apr 20, 2010 at 8:45 PM, Aniket Suryavanshi <ki...@gm...> wrote: >> checking for lt_dlopen in -lltdl... no >> configure: error: Could not find Libtool Libraries >> [root@globex ayttm-0.6.2]# > It says that you don;t have libtool libraries. You need to install libtool-ltdl-devel. -- Siddhesh Poyarekar http://siddhesh.in |
From: Aniket S. <ki...@gm...> - 2010-04-20 15:15:47
|
On Tue, Apr 20, 2010 at 8:38 PM, Kartik Mistry <kar...@gm...>wrote: > > > Hi Aniket, > > 'number of messages' must contain some error. ie. your ./configure is > not finished. Please paste output of ./configure using pastebin.com or > similar service. > > Thanks. > > -- > Cheers, > Kartik Mistry > Debian GNU/Linux Developer > 0xD1028C8D | Identica: @kartikm | IRC: kart_ > Blogs: {gu: kartikm, en: ftbfs}.wordpress.com > > Hi Kartik, All these messages were printed by *./configure*: [root@globex ayttm-0.6.2]# ./configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking for style of include used by make... GNU > checking dependency style of gcc... gcc3 > checking for strerror in -lcposix... no > checking for flex... flex > checking lex output file root... lex.yy > checking lex library... -lfl > checking whether yytext is a pointer... yes > checking for flex... flex > checking for bison... bison -y > checking for bison... bison > checking how to run the C preprocessor... gcc -E > checking for g++... g++ > checking whether we are using the GNU C++ compiler... yes > checking whether g++ accepts -g... yes > checking dependency style of g++... gcc3 > checking for g++... g++ > checking for ranlib... ranlib > checking build system type... x86_64-unknown-linux-gnu > checking host system type... x86_64-unknown-linux-gnu > checking for a sed that does not truncate output... /bin/sed > checking for grep that handles long lines and -e... /bin/grep > checking for egrep... /bin/grep -E > checking for fgrep... /bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1966080 > checking whether the shell understands some XSI constructs... yes > checking whether the shell understands "+="... yes > checking for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for ar... ar > checking for strip... strip > checking for ranlib... (cached) ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking whether we are using the GNU C++ compiler... (cached) yes > checking whether g++ accepts -g... (cached) yes > checking dependency style of g++... (cached) gcc3 > checking how to run the C++ preprocessor... g++ -E > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... no > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) yes > checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking for shl_load... no > checking for shl_load in -ldld... no > checking for dlopen... no > checking for dlopen in -ldl... yes > checking whether a program can dlopen itself... yes > checking whether a statically linked program can dlopen itself... yes > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for ld used by g++... /usr/bin/ld -m elf_x86_64 > checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes > checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking for g++ option to produce PIC... -fPIC -DPIC > checking if g++ PIC flag -fPIC -DPIC works... yes > checking if g++ static flag -static works... no > checking if g++ supports -c -o file.o... yes > checking if g++ supports -c -o file.o... (cached) yes > checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > Using Libtool for dynamic library loading > checking for windres... no > checking for _af_ulaw2linear in -laudiofile... no > checking for lt_dlopen in -lltdl... no > configure: error: Could not find Libtool Libraries > [root@globex ayttm-0.6.2]# > BTW I have a Fedora x64 version installed, which I had downloaded several months ago. Thanks, Aniket. -- *Aniket Suryavanshi* B.Sc. (Computer Science) student, India. aniket.wordpress.com twitter.com/kietan www.facebook.com/aniket1 |
From: Kartik M. <kar...@gm...> - 2010-04-20 15:09:18
|
On Tue, Apr 20, 2010 at 8:32 PM, Aniket Suryavanshi <ki...@gm...> wrote: > First I used the command ./configure Then a number of messages were printed > on screen. > > Then I used make. I got the following error: > make: *** No targets specified and no makefile found. Stop. Hi Aniket, 'number of messages' must contain some error. ie. your ./configure is not finished. Please paste output of ./configure using pastebin.com or similar service. Thanks. -- Cheers, Kartik Mistry Debian GNU/Linux Developer 0xD1028C8D | Identica: @kartikm | IRC: kart_ Blogs: {gu: kartikm, en: ftbfs}.wordpress.com |
From: Aniket S. <ki...@gm...> - 2010-04-20 15:03:07
|
On Mon, Apr 19, 2010 at 8:19 AM, Siddhesh Poyarekar < sid...@gm...> wrote: > On Sun, Apr 18, 2010 at 11:48 PM, Aniket Suryavanshi <ki...@gm...> > wrote: > > The first step (./configure) worked, but when I typed make and pressed > enter > > at the prompt, I got this error: > >> > >> ayt...@li... > > > > Could you paste the error again? You pasted the mailing list id again, > probably by mistake. > > Also, did you download the tarball or did you clone the git repository? > > > -- > Siddhesh Poyarekar > http://siddhesh.in > > I accidentally pasted wrong text in my last email. Sorry for that. I downloaded the project from http://sourceforge.net/projects/ayttm/Downloaded file had a * .tar.bz2* extension. I extracted the folder, opened the terminal and *cd *to this folder. First I used the command *./configure* Then a number of messages were printed on screen. Then I used *make*. I got the following error: > make: *** No targets specified and no makefile found. Stop. > Any help on this? Also, I checked out the TODO file. I prefer to work on MSN. -- *Aniket Suryavanshi* B.Sc. (Computer Science) student, India. aniket.wordpress.com twitter.com/kietan www.facebook.com/aniket1 |
From: Siddhesh P. <sid...@gm...> - 2010-04-19 02:49:40
|
On Sun, Apr 18, 2010 at 11:48 PM, Aniket Suryavanshi <ki...@gm...> wrote: > The first step (./configure) worked, but when I typed make and pressed enter > at the prompt, I got this error: >> >> ayt...@li... > Could you paste the error again? You pasted the mailing list id again, probably by mistake. Also, did you download the tarball or did you clone the git repository? -- Siddhesh Poyarekar http://siddhesh.in |
From: Aniket S. <ki...@gm...> - 2010-04-18 18:18:42
|
Hi, I just now downloaded the ayttm project from sourceforge. I was following the steps in file INSTALL. The first step (*./configure*) worked, but when I typed *make* and pressed enter at the prompt, I got this error: > *ayt...@li...* > Any help? I'm comfortable using C/C++, but I'm new to Linux. Any suggestions? -- *Aniket Suryavanshi* B.Sc. (Computer Science) student, India. aniket.wordpress.com twitter.com/kietan www.facebook.com/aniket1 |
From: Siddhesh P. <sid...@gm...> - 2010-04-13 09:28:50
|
On Mon, Apr 12, 2010 at 8:28 PM, Siddhesh Poyarekar <sid...@gm...> wrote: > On Mon, Apr 12, 2010 at 7:53 PM, Philip Tellis <phi...@gm...> wrote: >> what about people who build from source? > > They do not have this problem anyway, since they have the freedom to > enable/disable options as they wish. The problem is with a developer > looking to implement a yahoo client with devel packages from a distro > and finds that there are two completely different ways to do this and > he would have to find out which distro is using what way. That or > include a copy of libyahoo2 in his source, which is not good practice. > >> regarding freehoo, WITH_STRUCT_CALLBACKS should actually be the >> default, so perhaps you should push for them to change. >> > > Yes, they would have to end up making this change if libyahoo2 > provides only the callback interface. Currently, the Fedora release of > libyahoo2 is pulled from svn. As far as I could see, only freehoo > seems to be using it, so it should not be too difficult to get that > changed. Ray van Dolson is maintainer for both those packages for > Fedora and perhaps upstream for freehoo too. Is freehoo in Debian or > any other distro as well? How are they working things there? > Just went through sources of freehoo and turns out they're using callbacks too, along with using callback functions with the same name. Due to this the callbacks end up not being used and the functions are directly linked in. I have checked in the change into libyahoo2 as well. Will make changes here once that is released. -- Siddhesh Poyarekar http://siddhesh.in |
From: Siddhesh P. <sid...@gm...> - 2010-04-12 14:58:13
|
On Mon, Apr 12, 2010 at 7:53 PM, Philip Tellis <phi...@gm...> wrote: > what about people who build from source? They do not have this problem anyway, since they have the freedom to enable/disable options as they wish. The problem is with a developer looking to implement a yahoo client with devel packages from a distro and finds that there are two completely different ways to do this and he would have to find out which distro is using what way. That or include a copy of libyahoo2 in his source, which is not good practice. > regarding freehoo, WITH_STRUCT_CALLBACKS should actually be the > default, so perhaps you should push for them to change. > Yes, they would have to end up making this change if libyahoo2 provides only the callback interface. Currently, the Fedora release of libyahoo2 is pulled from svn. As far as I could see, only freehoo seems to be using it, so it should not be too difficult to get that changed. Ray van Dolson is maintainer for both those packages for Fedora and perhaps upstream for freehoo too. Is freehoo in Debian or any other distro as well? How are they working things there? -- Siddhesh Poyarekar http://siddhesh.in |
From: Philip T. <phi...@gm...> - 2010-04-12 14:24:14
|
On 12 April 2010 18:03, Siddhesh Poyarekar <sid...@gm...> wrote: > Hi, > > I was wondering if we could remove the libyahoo2 code base since it is > already a separate project. We can then have the yahoo2 plugin link to > libyahoo2 dynamically instead and pull that as dependency on rpm/deb > based systems. Is there any scenario where this will not be a good what about people who build from source? regarding freehoo, WITH_STRUCT_CALLBACKS should actually be the default, so perhaps you should push for them to change. |
From: Siddhesh P. <sid...@gm...> - 2010-04-12 14:21:20
|
On Mon, Apr 12, 2010 at 7:29 PM, Siddhesh Poyarekar <sid...@gm...> wrote: > > Ok, the first hurdle for this looks like the fact that we define > USE_STRUCT_CALLBACKS while the app for which libyahoo2 was included > into fedora (freehoo) does not seem to use it. > > Libyahoo2 needs to do this a little more flexibly so that one has the > option of either using the struct or defining functions individually. > I'll see how difficult that is to change. > Posted to libyahoo2-devel: https://sourceforge.net/mailarchive/forum.php?thread_name=j2x6e19a8cd1004120710i265def9fg50d4ee100ca01b9e%40mail.gmail.com&forum_name=libyahoo2-devel I've proposed removal of the direct linking option altogether so that we give all applications a consistent interface. -- Siddhesh Poyarekar http://siddhesh.in |
From: Siddhesh P. <sid...@gm...> - 2010-04-12 13:59:09
|
On Mon, Apr 12, 2010 at 6:09 PM, Kartik Mistry <kar...@gm...> wrote: > On Mon, Apr 12, 2010 at 6:03 PM, Siddhesh Poyarekar > <sid...@gm...> wrote: >> I was wondering if we could remove the libyahoo2 code base since it is >> already a separate project. We can then have the yahoo2 plugin link to >> libyahoo2 dynamically instead and pull that as dependency on rpm/deb >> based systems. Is there any scenario where this will not be a good >> idea? >> >> My primary motivation for doing this is that I need to pull in patches >> from libyahoo2 every time there is a change upstream. It is >> unnecessary overhead. > > +1 > > Please do this :) > Ok, the first hurdle for this looks like the fact that we define USE_STRUCT_CALLBACKS while the app for which libyahoo2 was included into fedora (freehoo) does not seem to use it. Libyahoo2 needs to do this a little more flexibly so that one has the option of either using the struct or defining functions individually. I'll see how difficult that is to change. -- Siddhesh Poyarekar http://siddhesh.in |
From: Kartik M. <kar...@gm...> - 2010-04-12 12:39:43
|
On Mon, Apr 12, 2010 at 6:03 PM, Siddhesh Poyarekar <sid...@gm...> wrote: > I was wondering if we could remove the libyahoo2 code base since it is > already a separate project. We can then have the yahoo2 plugin link to > libyahoo2 dynamically instead and pull that as dependency on rpm/deb > based systems. Is there any scenario where this will not be a good > idea? > > My primary motivation for doing this is that I need to pull in patches > from libyahoo2 every time there is a change upstream. It is > unnecessary overhead. +1 Please do this :) -- Cheers, Kartik Mistry Debian GNU/Linux Developer 0xD1028C8D | Identica: @kartikm | IRC: kart_ Blogs: {gu: kartikm, en: ftbfs}.wordpress.com |
From: Siddhesh P. <sid...@gm...> - 2010-04-12 12:33:33
|
Hi, I was wondering if we could remove the libyahoo2 code base since it is already a separate project. We can then have the yahoo2 plugin link to libyahoo2 dynamically instead and pull that as dependency on rpm/deb based systems. Is there any scenario where this will not be a good idea? My primary motivation for doing this is that I need to pull in patches from libyahoo2 every time there is a change upstream. It is unnecessary overhead. -- Siddhesh Poyarekar http://siddhesh.in |
From: Siddhesh P. <sid...@gm...> - 2010-03-22 06:39:37
|
On Mon, Mar 22, 2010 at 8:58 AM, Kartik Mistry <kar...@gm...> wrote: > Heya devs, > > Please see the log for hurd-i386 port in Debian: > https://buildd.debian.org/fetch.cgi?pkg=ayttm;ver=0.6.2-1;arch=hurd-i386;stamp=1266865346 > > Probably we can fix it with next version.. > This is probably a trivial fix. PATH_MAX does not seem to be recognized, so it is likely included implicitly (or in a different header) in Linux as opposed to GNU/Hurd. I don't have time for it right now, so I'll look at it over the weekend. Does anyone on list want to give it a try till then? -- Siddhesh Poyarekar http://siddhesh.in |
From: Kartik M. <kar...@gm...> - 2010-03-22 03:29:10
|
Heya devs, Please see the log for hurd-i386 port in Debian: https://buildd.debian.org/fetch.cgi?pkg=ayttm;ver=0.6.2-1;arch=hurd-i386;stamp=1266865346 Probably we can fix it with next version.. -- Cheers, Kartik Mistry | 0xD1028C8D | IRC: kart_ Debian GNU/Linux Developer | Identica: @kartikm Blogs: {ftbfs, kartikm}.wordpress.com |
From: Siddhesh P. <sid...@gm...> - 2010-02-19 05:23:11
|
Here is another release of ayttm with a bunch of improvements, especially to the UI code: * Reworked chat window look and also under the hood. The code is much cleaner as a result * Fixed some linker related bugs raised in Fedora and Debian bug trackers * Clean up the chat notifications (Buddy arrive,, leave, etc.) * IRC kick. Go kick your buddy now ;) * expat security fixes (CVE-2009-3560 CVE-2009-3720) * Yahoo Buzz * Yahoo address book fixes * Fixed multiple buffer overflows and crashes in MSN and Yahoo * Enchat/hunspell support for spell check. This replaces aspell Here is the complete Changelog of updates since the last release. http://ayttm.git.sourceforge.net/git/gitweb.cgi?p=ayttm/ayttm;a=blob;f=ChangeLog;h=424e0c02e1c011395d63657fcfafd00126197aaf;hb=HEAD -- Siddhesh Poyarekar http://siddhesh.in |
From: Kartik M. <kar...@gm...> - 2010-02-19 04:35:29
|
On Fri, Feb 19, 2010 at 9:57 AM, Siddhesh Poyarekar <sid...@gm...> wrote: > The fixes are already in git, so they'll make it in the release. > There's another bug that's open in Debian which requests removal of > the expat code from inside ayttm completely. I'm thinking of rewriting > the jabber module in the future, so that may well happen. But not this > release. Cool. No issue. I'm updating #561006. -- Cheers, Kartik Mistry | 0xD1028C8D | IRC: kart_ Debian GNU/Linux Developer | Identica: @kartikm Blogs: {ftbfs, kartikm}.wordpress.com |