I think of two possible reasons:
- Different compiling optimization (O1? O2?)
- Stripping

I can't follow your discussion but I thought I'd put in a cheer for the work you're doing.

In the recently released update I beleive it has broken MSN (I have rtcomm). I use jabber, gtalk and aim. AIM never connects and msn doesnt even load if anything else is in use. The second you enable other accounts it breaks msn.

My device has just notified me of an update for ...
OS2008 Community SSU, version 1:52010.14-2

Just finished installing ....

I can't seem to see what the difference is from the 14-1 version .

Will it be possible to put a small note in this thread (or highlight the changes from the previous version) so we know what to test for?


thanks ...

so far .... all seems to work ok.

Both binaries are stripped of course. It would be nice to know whether the official binaries are built with the same toolchain, but other than that the only way I can think of that compilation flags could differ between builds of the same source package is if the two build systems have different gcc.specs.

But, you know what's funny, I thought to check if this still applies to Fremantle and sure enough there's also a significant size discrepancy there, but in the opposite direction!

Original PR1.1.1 /bin/busybox from .deb (1.10.2.legal-1osso26+0m5): 355592 bytes.
Local rebuild of the same source package: 253196 bytes.

This is on a '5.0-final' SDK that has been apt-get upgraded to PR1.2, ie it's scratchbox 1.0.16 under the hood (the current SDK ships 1.0.14 for some reason). My Diablo SDK is a separate installation, using scratchbox 1.0.11.

This may be worthy of a bug report even, as it could suggest an easy way to shave a few MiBs off the Fremantle rootfs.

The only difference is fixing the -unlocked meta-packages (mentioned in post #261).

I assume you mean rtcomm beta? Can anyone confirm that these protocols are still supposed to work on Diablo? ISTR some reports that they were broken in Fremantle, but I never had any interest in proprietory IM protocols personally so never paid much attention.

Do you know which package(s) on your system implement support for MSN/AIM? Could you also PM me the output of "dpkg -l"? Some syslog output (see here) might be helpful too, if you can.

The only change in the telepathy stack (a small workaround in loudmouth to stop telepathy-gabble spinning) shouldn't affect non-XMPP protocols in any way.

I enabled the Red Pill mode on my tablet and found some updates available and was wondering if it would be safe or useful to update these packages?

The packages available for update are these:

gstreamer0.10-plugins-bad-ivorbis ver. 0.10.5-9
libmad0 ver. 0.15.1b-2.1maemo1
libpurple0 ver. 2.6.6-0nix1
libxcomposite1 ver. 0.4.0-3
libxml2 ver. 2.6.27.dfsg-1.maemo1
poppler-utils ver. 0.10.5-1maemo1
python-gdata ver. 1.2.3-0maemo2
telepathy-haze ver. 0.2.1-2
x11-common ver. 7.4-5maemo3

I can update this packages for testing with the SSU.

Thanks.

None of these packages come from the SSU repository, and a few conflict with the versions depended on by osso-software-version and would cause it to be uninstalled thus breaking future updates. You might get better results with osso-software-version-rxXX-unlocked, but if it breaks you get to keep both pieces ;-)

rtcomm beta has worked perfectly fine with me in the past. Msn now no longer works... I'll post my dpkg... errr, pm it.
Edit: MSN only dies when aim tries to connect. Otherwise Msn works fine...