Bug 29275 – Version bump on MSN gateway to handle change in protocol

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Gustavo Felisberto (RETIRED) 2003-09-21 10:36:48 UTC]

As of 14 of october all msn clients will have to user version 8 of the protocol.
This ebuild comes with updated version on the msn transport.

Also i am working on a new set of ebuilds for jabberd that will make upgrades of 
transports easier (separating everything). I alread have jabberd and msn 
ebuilds, when i have it alll i will submitt.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Gustavo Felisberto (RETIRED) 2003-09-21 10:38:42 UTC]

Created attachment 18082 [details]
jabber-server-1.4.2-r4.ebuild

[Comment 2 Gustavo Felisberto (RETIRED) 2003-09-22 09:51:55 UTC]

This is borked... I am working in a new ebuild... dont comit this one....

[Comment 3 Gustavo Felisberto (RETIRED) 2003-09-22 11:13:18 UTC]

Created attachment 18137 [details]
jabber-server-1.4.2-r4.tar.gz

I tought it was just a small version bump, but some things needed change in the
ebuild.

[Comment 4 Gustavo Felisberto (RETIRED) 2003-09-22 13:47:06 UTC]

Created attachment 18147 [details]
jabber-server-1.4.2-r4.tar.bz2

After installing in a production server where there was no curl i noticed that
the new msn gateways depends on libcurl. This is the new version and also
updated configs because new msn gateway comes with a few extra configurable
stuff (config for older version still works but will not take advantage of new
features).

[Comment 5 Gustavo Felisberto (RETIRED) 2003-09-22 13:50:26 UTC]

This is probably safe now and good for upgrade.
Some other gateways need upgrade, but they are not so critical, and i will update them on the new release (separated ebuilds for jabberd wpjabber jabberd2 and gateways).

[Comment 6 Luke-Jr 2003-09-22 18:34:28 UTC]

However, as I cannot test jabber-server at the moment, this change will also need to wait for bug 26440 before I can implement it.

[Comment 7 Luke-Jr 2003-10-05 11:46:34 UTC]

I changed it as what seems to be correct, but I cannot get the new MSN transport
to work locally. -r4 is now in Portage, but without any keywords. If someone
could take a look at it and let me know what's wrong, it'll probably be fixed
much sooner than otherwise.

[Comment 8 Gustavo Felisberto (RETIRED) 2003-10-10 10:43:43 UTC]

The multiple.xml has:
<service id="msnlinker">              <!-- msn data -->
    <host>msn.localhost</host>          <!-- msn data -->
    <accept>                            <!-- msn data -->
      <ip>127.0.0.1</ip>                <!-- msn data -->
      <port>5613</port>                 <!-- msn data -->
      <secret>mymsnsecret</secret>      <!-- msn data -->
    </accept>                           <!-- msn data -->
</service>

and msntrans.xml
 <service id="msnlinker">
    <uplink/>
    <connect>
      <ip>127.0.0.1</ip>
      <port>1234</port>
      <secret>test</secret>
    </connect>
  </service>

Did you change the port secret to be the same in both files? Maybe a good
idea to do that in the config. I will post a config-1.4.2-r4.tbz2 in a few
minutes

[Comment 9 Gustavo Felisberto (RETIRED) 2003-10-10 10:47:49 UTC]

Created attachment 19058 [details]
new .xml files

[Comment 10 Luke-Jr 2003-10-10 17:53:21 UTC]

Still does not work after changing secrets to match.

[Comment 11 Luke-Jr 2003-10-10 18:54:48 UTC]

Completed successfully in jabber-server-1.4.2-r4 (~x86).