rtcomm update problem
 

can anyone tell me how to rexsolve this issue with the new update for rtcomm?

Re: rtcomm update problem
 

Yeah I'm seeing the same thing

Re: rtcomm update problem
 

I have the same thing here. It looks like the packages for Maemo haven't been compiled yet: they exist for Debian (http://packages.collabora.co.uk/debi...elepathy-haze/), but not for Maemo :(

I guess it's just a matter of time before they are available...

Re: rtcomm update problem
 

OK nevermind, I've found the solution:

- go to application manager
- main menu -> tools -> application catalogue
- for the collabora repository, remove everything in the "Components" line, and replace with "user"
- click OK: the packages list will refresh and rtcomm-beta will be updateable...

Edit: it should also be possible to replace chinook with diablo (if you are using diablo, and you have specified a specific distribution) in the distribution line...apparently packages for Diablo are available (in the end they are the same, but I prefer not having too much dependencies on old stuff found in chinook...)

Re: rtcomm update problem
 

I solved this problem another way.... I installed http://rtcomm.garage.maemo.org/deb/r..._0.6_armel.deb then ran the install script it puts in your Extras menu. I haven't looked into what's new with this version yet. Anyone know? I don't know if it's related, but this update could have messed with my 2.4.3 pidgin install.

Re: rtcomm update problem
 

I still haven't found out what's new with this version, but it's very possible that it may have messed your pidgin install: one of the updated libraries from collabora repository is libpurple, which is used by Pidgin....

And it looks like Pidgin is also distributed by Collabora, so maybe it overwrote your install of Pidgin from another source? (I really don't know how AppManager manages these situations, but I suspect that it will try to install the latest version it finds, even if it comes from another source?)

Re: rtcomm update problem
 

Also see
https://bugs.maemo.org/show_bug.cgi?id=3546

Re: rtcomm update problem
 

Yeah, my mistake was probably installing the Collabora pidgin and libpurple0 update. I did a bunch of stuff to fix pidgin, unfortunately I don't remember it all. I was poking around. Basicly I had to uninstall pidgin and everything pidgin related. It ended up a smilies add-on was causing the install to break. After this I was able to do a apt-get install libpurple0 and I forget what else... apt-get install pidgin-data maybe? Anyways, even after I got pidgin installed, I couldn't launch it from personal menu. I had to remove the DBUS service name. It was a mess but I got it working at the end.

Re: rtcomm update problem
 

the reason for the problem is that pidgin-data conflicts with some of the other packages of rtcomm this is because rtcomm splitted the data packages more refined (e.g. pidgin-sounds, pidgin-otr, etc etc)

If you use apt-get or dpkg to install you can see the details.

Re: rtcomm update problem
 

have the same problem... just change the collabora repo to diablo and it will install.