SVN can't be compiled

[Jury]

Hello. I guess I should warn you that SVN trunk can't be compiled via
make at the moment due to some problems with MonoDevelop makefile
integration. Draekz is sorting the issue out, so you don't need to
post any bugreports about it.

We may actually abandon autotools completely in favor of much simplier
xbuild approach, but we haven't figured out, yet, what would the
implications be for the PPA repository for Ubuntu.

So, if there is someone with experience in deploying non-autotools
based projects via PPA, help would be very appreciated :)

[dbercot]

Hi,

Maybe I've not understood everything, but I can compile !?!?
Now, I use the build 1322 and everything seems ok.

I have another problem : Galaxium can connect with Jabber, but not
with
MSN :
[I've removed some lines]
Warning: Deleting invalid cached security token
4F211A68D7596313482D1526CCCA256E Debug: P2PBridge 1:UUNBridge created
Info: Using MSN Protocol Version MSNP15
Debug: Security tokens expired or not present, requesting new ones
Debug: Switching to Url https://login.live.com/RST.srf
Debug: Invoking RequestMultipleSecurityTokens (attempt 1 of 10) on
https://login.live.com/RST.srf Debug: Received 20% (1792 of 8788
bytes)
Debug: Received 40% (3584 of 8788 bytes)
Debug: Received 90% (7936 of 8788 bytes)
Debug: Received 100% (8788 of 8788 bytes)
Debug: Invoke RequestMultipleSecurityTokens on
https://login.live.com/RST.srf successful on attempt 1 Debug: No valid
cached address book, requesting it all Debug: Required security tokens
all OK, no request needed Debug: Switching to Url
https://omega.contacts.msn.com/abservice/SharingService.asmx Debug:
Invoking FindMembershipDelta (attempt 1 of 10) on
https://omega.contacts.msn.com/abservice/SharingService.asmx Debug:
Required security tokens all OK, no request needed Debug: Switching to
Url https://by4.omega.contacts.msn.com/abservice/abservice.asmx Debug:
Invoking ABFindAll (attempt 1 of 10) on
https://by4.omega.contacts.msn.com/abservice/abservice.asmx Debug:
Received 80% (3328 of 4118 bytes) Debug: Received 100% (4118 of 4118
bytes) Debug: Invoke FindMembershipDelta on
https://omega.contacts.msn.com/abservice/SharingService.asmx
successful
on attempt 1 Error: Unable to retreive memberships A null value was
found where an object instance was required. at
Galaxium.Protocol.Msn.Soap.BodyParts.Member.ApplyDelta
(Galaxium.Protocol.Msn.Soap.BodyParts.Member m) [0x00000] at
Galaxium.Protocol.Msn.Soap.BodyParts.PassportMember.ApplyDelta
(Galaxium.Protocol.Msn.Soap.BodyParts.Member m) [0x00000] at
Galaxium.Protocol.Msn.MsnSession.UpdateMemberships
(Galaxium.Protocol.Msn.Soap.BodyParts.FindMembershipResult result)
[0x00000] at Galaxium.Protocol.Msn.NSConnection.MembershipsFound
(IAsyncResult asyncResult) [0x00000] Debug: Disconnecting during
disposing of abstract connection. Debug: Firing closed event. Debug:
The connection ended as expected. Debug: Received 10% (5120 of 50246
bytes) Debug: Received 20% (10240 of 50246 bytes) Debug: Received 30%
(15104 of 50246 bytes) Debug: Received 40% (20167 of 50246 bytes)
Debug: Received 50% (25287 of 50246 bytes) Debug: Received 60% (30151
of 50246 bytes) Debug: Received 70% (35271 of 50246 bytes) Debug:
Received 80% (40391 of 50246 bytes) Debug: Received 90% (45255 of
50246
bytes) Debug: Received 100% (50246 of 50246 bytes) Debug: Invoke
ABFindAll on
https://by4.omega.contacts.msn.com/abservice/abservice.asmx successful
on attempt 1 Debug: Removing old cached
addressbook /home/david.bercot/.config/Galaxium/Cache/MSN/
550776C7E681ED892D1D3E702C0BD806/
addressbook_2009-04-08T00:32:59.157-07:00

If anyone has an idea...

Thanks.

David.

[Jiří Zárevúcký]

2009/4/9 dbercot <goo...@bercot.org>:

>
> Maybe I've not understood everything, but I can compile !?!?
> Now, I use the build 1322 and everything seems ok.
>

What distribution do you use? It seemed to work only on some systems.
Revision 1323 should be ok.

> I have another problem : Galaxium can connect with Jabber, but not
> with MSN :

Yeah, we know about this problem. What version of Mono are you using?

[dbercot]

On Apr 9, 9:46 pm, Jiří Zárevúcký <zarevucky.j...@gmail.com> wrote:
> 2009/4/9 dbercot <goo...@bercot.org>:
>
> > Maybe I've not understood everything, but I can compile !?!?
> > Now, I use the build 1322 and everything seems ok.
>
> What distribution do you use? It seemed to work only on some systems.
> Revision 1323 should be ok.

I'm under Debian [amd64], kernel 2.6.29.

> > I have another problem : Galaxium can connect with Jabber, but not
> > with MSN :
>
> Yeah, we know about this problem. What version of Mono are you using?

apt-cache policy mono-runtime
mono-runtime:
Installé : 2.0.1-5

Thanks.

David.

[Jiří Zárevúcký]

2009/4/9 dbercot <goo...@bercot.org>:
>> > Maybe I've not understood everything, but I can compile !?!?
>> > Now, I use the build 1322 and everything seems ok.
>>
>> What distribution do you use? It seemed to work only on some systems.
>> Revision 1323 should be ok.
>
> I'm under Debian [amd64], kernel  2.6.29.
>

As I expected.

>> > I have another problem : Galaxium can connect with Jabber, but not
>> > with MSN :
>>
>> Yeah, we know about this problem. What version of Mono are you using?
>
> apt-cache policy mono-runtime
> mono-runtime:
>  Installé : 2.0.1-5
>

Now that's weird. It should run fine with 2.0.

[Draek]

yeah, I'm using Ubuntu (9.04) Jaunty 32-bit and Mono 2.0.1, mine is
able to connect. Basically David, i would say go into the issues
section and open up a new bug report if you like. I just finally got
back up to speed and I am going to be working on the code starting
this week.

Give us a bug report including the entire log. The best thing would be
to start a new log that includes only the connecting to 1 single
protocol.

Make sure to re-start the application before logging so there is no
other logins or chat details.

OH! Also, if you are still using the Proxy stuff, let me know. It may
not be the protocol handlers that are problematic, but the Connection
itself.

THANKS!

Draek

[dbercot]

Hi Phil,

Nice to read you ;-)

On Apr 13, 2:10 am, Draek <dra...@gmail.com> wrote:
> yeah, I'm using Ubuntu (9.04) Jaunty 32-bit and Mono 2.0.1, mine is
> able to connect. Basically David, i would say go into the issues
> section and open up a new bug report if you like. I just finally got
> back up to speed and I am going to be working on the code starting
> this week.

Yes, good news !!!

> Give us a bug report including the entire log. The best thing would be
> to start a new log that includes only the connecting to 1 single
> protocol.
> Make sure to re-start the application before logging so there is no
> other logins or chat details.

Before reporting a bug, I'm doing other tries on several computers...
But I have some problems.

First of all, on a computer, I have this error (I don't understand at
all) :
apt-get build-dep galaxium-svn
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture de l'information d'état... Fait
E: Les dépendances de compilation pour galaxium-svn ne peuvent pas
être satisfaites.

Second, on the last build (1364), I can't compile (I think I miss
something) :
./FBSession.cs(34,7): error CS0246: The type or namespace name
`facebook' could not be found. Are you missing a using directive or an
assembly reference?
./FBSession.cs(34,7): error CS0246: The type or namespace name
`facebook' could not be found. Are you missing a using directive or an
assembly reference?
Compilation failed: 2 error(s), 0 warnings
make[3]: *** [../../../build/Galaxium.Protocol.Facebook.dll] Erreur 1
make[3]: quittant le répertoire « /opt/galaxium-read-only/src/
Protocols/Galaxium.Protocol.Facebook »
make[2]: *** [install-recursive] Erreur 1
make[2]: quittant le répertoire « /opt/galaxium-read-only/src/
Protocols »
make[1]: *** [install-recursive] Erreur 1
make[1]: quittant le répertoire « /opt/galaxium-read-only/src »
make: *** [install-recursive] Erreur 1

Well, we'll be able to see our Facebook's contacts with Galaxium ?
And what about Twitter ?

> OH! Also, if you are still using the Proxy stuff, let me know. It may
> not be the protocol handlers that are problematic, but the Connection
> itself.

I understand but I have the problem at work (with the proxy) and at
home (without it)...

Thanks.

David.

[Jiří Zárevúcký]

2009/4/14 dbercot <goo...@bercot.org>:

>
> First of all, on a computer, I have this error (I don't understand at
> all) :
> apt-get build-dep galaxium-svn
> Lecture des listes de paquets... Fait
> Construction de l'arbre des dépendances
> Lecture de l'information d'état... Fait
> E: Les dépendances de compilation pour galaxium-svn ne peuvent pas
> être satisfaites.
>

That makes two of us. :D Can't you post error logs in english? (LANG=C
whatever-command-you-need)

> Well, we'll be able to see our Facebook's contacts with Galaxium ?
> And what about Twitter ?
>

Yup, Phil's working on that now. For Twitter you'll have to wait a bit
longer I guess... Or code it yourself ;)