Opened 16 years ago

Closed 16 years ago

Last modified 16 years ago

#15955 closed defect (fixed)

Finch no longer connects to ICQ

Reported by: xoagray@… Owned by: rsync@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: Finch ICQ Cc: simon@…
Port:

Description

On trying to connect Finch version 2.3.1 to ICQ, the error "│The client version you are using is too old. Please upgrade at http://pidgin.im/ " appears. Finch will not connect to ICQ.

Attachments (1)

finch-2.4.3.patch (1.8 KB) - added by simon@… 16 years ago.

Download all attachments as: .zip

Change History (18)

comment:1 Changed 16 years ago by xoagray@…

Found this on the Pidgin website, thought it would be a good idea to post here.

Suddenly we started seeing reports about ICQ no longer working in #pidgin. Upon investigation we discovered that apparently the client ID has been "retired", and any logins from that client ID are immediately met with a message from the server demanding an upgrade to ICQ6. The server then forcibly disconnects us. We catch this error and display a somewhat different message instructing our users to go to pidgin.im to get an update.

Stu Tomlinson found the version identification information for the most current official ICQ client and changed our identification. Magically logging in and holding a conversation works. This patch became the reason for the release of Pidgin 2.4.3.

Thank you

comment:2 Changed 16 years ago by blb@…

Owner: changed from macports-tickets@… to rsync@…

Assign to maintainer.

comment:3 Changed 16 years ago by simon@…

Cc: simon@… added

Here is a patch to update to 2.4.3 which works fine for me.

Simon

Changed 16 years ago by simon@…

Attachment: finch-2.4.3.patch added

comment:4 Changed 16 years ago by xoagray@…

I tried running the patch, and it says this.

pathcing file finch Hunk #1 FAILED at 3. Hunk #2 FAILED at 20. Hunk #3 FAILED at 39.

I may be doing something wrong, I'm not all that familiar with patching under Unix. I typed in "sudo patch finch (path to finch patch)"

comment:5 Changed 16 years ago by simon@…

To use the patch you can use the following:

cd $(port dir finch)
sudo patch -p2 < path_to_finch_patch

This will patch finch. -p2 means to strip the first two directories from the patch strings. This is necessary as I used net/finch/Portfile in the patch. Normally -p0 or -p1 is used. For more information have a look at http://en.wikipedia.org/wiki/Patch_%28Unix%29.

comment:6 Changed 16 years ago by simon@…

Resolution: fixed
Status: newclosed

Committed in r38190. To update wait about 12 hours then use sudo port selfupdate; sudo port upgrade finch to upgrade it.

If you used my patch this is not necessary as you then have already the latest version installed.

Simon

comment:7 Changed 16 years ago by xoagray@…

Hmm, I've done just what you described to run the patch. But for some reason, it seems to just hang. I let it sit for 15 minutes and it didn't do anything. I think I'm just going to wait for the update.

Thank you very much.

comment:8 Changed 16 years ago by simon@…

Weird. This works for me. But the update should be available by now. So sudo port selfupdate; sudo port upgrade finch should work fine.

You're welcome.

comment:9 Changed 16 years ago by xoagray@…

Okay, I tried upgrading Finch, and it came back failing. So I uninstalled 2.3.1 and tried installing 2.4.3. However, now it won't install. Gives an error when configuring that I've posted here,

http://docs.google.com/Doc?id=ddq2wg9c_14csbpxtdg

for the sake of keeping this entry neat. I tried installing and uninstalling a few other programs, to make sure that my install of MacPorts wasn't botched up, everything went fine. Just seems that it won't compile this new version of Finch. If it makes a difference, I'm using OS X 10.4.11

comment:10 Changed 16 years ago by simon@…

The "problem" is that finch is looking for dbus, but as it's not necessary I disabled it in r38208. To do this manually just run open $(port dir finch) and make the following change by hand (no patching necessary as it's only one line). It's possible that the file may not exactly look like this patch, don't worry, just add the line at configure.args:

--- Portfile
+++ Portfile
@@ -34,6 +34,7 @@ depends_lib         port:audiofile \
 patchfiles          patch-finch_libgnt_Makefile.in.diff
 
 configure.args      --disable-avahi \
+                    --disable-dbus \
                     --disable-gstreamer \
                     --disable-gtkspell \
                     --disable-gtkui \

Then finch should build fine (I hope).

comment:11 Changed 16 years ago by xoagray@…

I have no "Finch" directory. when it wouldn't upgrade, I thought it would be easier to just uninstall it, then reinstall it, but it won't compile to reinstall. I've been looking through the directory that Finch was in, going through any file I've got that has "port" in the name, but can't find one line that says "configure.args" to add --disable-dbus to. I may be looking in the wrong place, I figured as you said "port dir finch" you meant the directory that finch was in. So I've been going through every "port" related file in opt/local/bin.

comment:12 Changed 16 years ago by xoagray@…

Alternative fix. I entered "sudo port --disable-dbus install finch", and that changed the portfile, and allowed Finch to successfully install. Sorry if my inexperience has been a pain, I'm still learning.

comment:13 in reply to:  12 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to xoagray@gmail.com:

I have no "Finch" directory. when it wouldn't upgrade, I thought it would be easier to just uninstall it, then reinstall it, but it won't compile to reinstall. I've been looking through the directory that Finch was in, going through any file I've got that has "port" in the name, but can't find one line that says "configure.args" to add --disable-dbus to. I may be looking in the wrong place, I figured as you said "port dir finch" you meant the directory that finch was in. So I've been going through every "port" related file in opt/local/bin.

He meant you should type exactly the characters "open $(port dir finch)" (without the quotation marks) into a Terminal window. This will open into the Finder the directory containing the finch Portfile which you can then open in your favorite editor and change as per his instructions. But those instructions are no longer necessary since the port has already been updated. Simply type "sudo port selfupdate" (without the quotes) to get the new version and then install the port as usual.

Replying to xoagray@gmail.com:

Alternative fix. I entered "sudo port --disable-dbus install finch", and that changed the portfile, and allowed Finch to successfully install. Sorry if my inexperience has been a pain, I'm still learning.

That can't have done anything helpful. The "port" command does not have a "--disable-dbus" option; rather, finch's configure script does. If you were able to install finch, then you already had the updated Portfile. On my system, trying to use port --disable-dbus install finch gives this error message, as well it should:

global does not accept --disable-dbus
    while executing
"parse_options "global" ui_options global_options"
    (file "/opt/local/bin/port" line 3172)

comment:14 Changed 16 years ago by xoagray@…

Well, again, I do apologize for my inexperience. I'm new to this, and admit that I don't know exactly what I'm doing. All I know is that when I typed what I did, at the time, it did work, and Finch did install. If that was coincidental, so be it. I did try to repeat the same thing today, and now it does as you said it would. Does Port automatically get new portfiles when it tries to install software? Not trying to be a burden here, just trying to understand what happened.

comment:15 in reply to:  14 Changed 16 years ago by simon@…

Replying to xoagray@gmail.com:

Well, again, I do apologize for my inexperience.

No need to apologize ;-)

Replying to xoagray@gmail.com:

[snip] Does Port automatically get new portfiles when it tries to install software? Not trying to be a burden here, just trying to understand what happened.

No. Only after running sudo port selfupdate or sudo port sync your Portfiles are updated.

But as it worked and you got a running finch, don't worry be happy :-)

Simon

comment:16 Changed 16 years ago by xoagray@…

That's cool. But the more I understand it, the less I'll make mistakes in here. :)

Thanks again.

comment:17 Changed 16 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.