Re: libosso-abook-1.0 and librtcom-eventlogger
Hi Saurabh! Have you heard about Windows Vista? Thanks, Daniil. On Tue, Jun 22, 2010 at 8:20 AM, saurabh aggarwal aggarwal.saur...@gmail.com wrote: So, are we supposed to produce multiple binaries for every version of Maemo platform? That doesn't sound right. Unfortunately, I am new to linux applications and have always had my old apps working on new versions of Windows (without a re-compile). So, am a bit confused. -Saurabh On Tue, Jun 22, 2010 at 2:54 AM, Daniil Ivanov daniil.iva...@gmail.com wrote: Hi Saurabh! It depends on library. In general case answer is no. Thanks, Daniil. On Mon, Jun 21, 2010 at 6:30 PM, saurabh aggarwal aggarwal.saur...@gmail.com wrote: Once, I upgrade the SDK, would the produced library still be compatible with devices which don't have PR 1.2 installed? Regards, -Saurabh On Mon, Jun 21, 2010 at 6:56 PM, Daniil Ivanov daniil.iva...@gmail.com wrote: Hi Saurabh! Upgrade your SDK with fakeroot apt-get update fakeroot apt-get dist-upgrade Thanks, Daniil. On Mon, Jun 21, 2010 at 3:47 PM, saurabh aggarwal aggarwal.saur...@gmail.com wrote: We were building out application and testing on N900 with PR1.1. We recently upgraded our device to PR1.2, and now are getting error when we try to launch it. The error we get is error while loading shared libraries: librtcom-eventlogger.so. I checked in the pro file, and we are using libosso-abook-1.0 which is adding the dependency for this library which seems to be non-compatible from previous version. How should I handle this in my application? Does this mean that I can't use libosso-abook-1.0 anymore, or do I need to update my dev libraries ? BTW, I did try to check and there wasn't an update to libosso-abook-dev available. -Saurabh ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: libosso-abook-1.0 and librtcom-eventlogger
What you should do is to include strict dependency to libosso-abook-1.0 in dependencies of your package. Then during installation process of your application apt will automatically pull the newer versions of libraries on devices with PR1.1. Thanks, Daniil. On Tue, Jun 22, 2010 at 10:57 AM, Daniil Ivanov daniil.iva...@gmail.com wrote: Hi Saurabh! Have you heard about Windows Vista? Thanks, Daniil. On Tue, Jun 22, 2010 at 8:20 AM, saurabh aggarwal aggarwal.saur...@gmail.com wrote: So, are we supposed to produce multiple binaries for every version of Maemo platform? That doesn't sound right. Unfortunately, I am new to linux applications and have always had my old apps working on new versions of Windows (without a re-compile). So, am a bit confused. -Saurabh On Tue, Jun 22, 2010 at 2:54 AM, Daniil Ivanov daniil.iva...@gmail.com wrote: Hi Saurabh! It depends on library. In general case answer is no. Thanks, Daniil. On Mon, Jun 21, 2010 at 6:30 PM, saurabh aggarwal aggarwal.saur...@gmail.com wrote: Once, I upgrade the SDK, would the produced library still be compatible with devices which don't have PR 1.2 installed? Regards, -Saurabh On Mon, Jun 21, 2010 at 6:56 PM, Daniil Ivanov daniil.iva...@gmail.com wrote: Hi Saurabh! Upgrade your SDK with fakeroot apt-get update fakeroot apt-get dist-upgrade Thanks, Daniil. On Mon, Jun 21, 2010 at 3:47 PM, saurabh aggarwal aggarwal.saur...@gmail.com wrote: We were building out application and testing on N900 with PR1.1. We recently upgraded our device to PR1.2, and now are getting error when we try to launch it. The error we get is error while loading shared libraries: librtcom-eventlogger.so. I checked in the pro file, and we are using libosso-abook-1.0 which is adding the dependency for this library which seems to be non-compatible from previous version. How should I handle this in my application? Does this mean that I can't use libosso-abook-1.0 anymore, or do I need to update my dev libraries ? BTW, I did try to check and there wasn't an update to libosso-abook-dev available. -Saurabh ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: libosso-abook-1.0 and librtcom-eventlogger
So, you mean if we build with PR 1.2 SDK, then if the dependencies are correctly setup, the resulting build should work for PR 1.1 as well (as PR 1.1 will be automatically updated). We did find that the binary we made with the PR 1.1 SDK, when installed on PR 1.2 device, the layout is not consistent with what it is on PR 1.1 device. Would the layout be consistent on PR1.1 if we used the PR 1.2 SDK or do we have to build a strict dependency for the QT library as well :). I hope we are not planning on Maemo to have the same fate as Vista (so, please don't justify with the Vista experience). Most companies I know (including ours) skipped Vista. Windows 7 is great though. -Saurabh On Tue, Jun 22, 2010 at 2:08 PM, Daniil Ivanov daniil.iva...@gmail.comwrote: What you should do is to include strict dependency to libosso-abook-1.0 in dependencies of your package. Then during installation process of your application apt will automatically pull the newer versions of libraries on devices with PR1.1. Thanks, Daniil. On Tue, Jun 22, 2010 at 10:57 AM, Daniil Ivanov daniil.iva...@gmail.com wrote: Hi Saurabh! Have you heard about Windows Vista? Thanks, Daniil. On Tue, Jun 22, 2010 at 8:20 AM, saurabh aggarwal aggarwal.saur...@gmail.com wrote: So, are we supposed to produce multiple binaries for every version of Maemo platform? That doesn't sound right. Unfortunately, I am new to linux applications and have always had my old apps working on new versions of Windows (without a re-compile). So, am a bit confused. -Saurabh On Tue, Jun 22, 2010 at 2:54 AM, Daniil Ivanov daniil.iva...@gmail.com wrote: Hi Saurabh! It depends on library. In general case answer is no. Thanks, Daniil. On Mon, Jun 21, 2010 at 6:30 PM, saurabh aggarwal aggarwal.saur...@gmail.com wrote: Once, I upgrade the SDK, would the produced library still be compatible with devices which don't have PR 1.2 installed? Regards, -Saurabh On Mon, Jun 21, 2010 at 6:56 PM, Daniil Ivanov daniil.iva...@gmail.com wrote: Hi Saurabh! Upgrade your SDK with fakeroot apt-get update fakeroot apt-get dist-upgrade Thanks, Daniil. On Mon, Jun 21, 2010 at 3:47 PM, saurabh aggarwal aggarwal.saur...@gmail.com wrote: We were building out application and testing on N900 with PR1.1. We recently upgraded our device to PR1.2, and now are getting error when we try to launch it. The error we get is error while loading shared libraries: librtcom-eventlogger.so. I checked in the pro file, and we are using libosso-abook-1.0 which is adding the dependency for this library which seems to be non-compatible from previous version. How should I handle this in my application? Does this mean that I can't use libosso-abook-1.0 anymore, or do I need to update my dev libraries ? BTW, I did try to check and there wasn't an update to libosso-abook-dev available. -Saurabh ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: libosso-abook-1.0 and librtcom-eventlogger
On Tuesday 22 June 2010 06:20:26 saurabh aggarwal wrote: So, are we supposed to produce multiple binaries for every version of Maemo platform? That doesn't sound right. The answer is: it depends. In general in Linux, an application developed on one version will often work on later versions (the opposite is not true: applications built on one version normally do not work on earlier versions). There can be major break points for which this is not true, and the more libraries you use the more likely you will hit a break point. In this, Linux is very much like Windows but it is fair to say that Linux distributions do not make as much effort over this as Windows. Don't forget that in the Linux world, most applications are open and are fully recompiled by the distribution -- closed aplications are the exception. This is opposite to the Windows case. However, Maemo is a bit different. It is a special-purpose, embedded platform and it does not attempt to provide a general purpose platform. If you don't use any of the device special features (no graphics, no location, no sound, no ...) then it is possible your app will work on all Maemo devices from the 770 on. In practice that is limited to command line file manipulation utilities (like diff, say). No attempt is made to keep graphics libraries compatible between major releases. So graphical apps for Maemo 4 (N800/N810) do not work on Maemo 5 (N900), That is not a big problem -- these are different devices. Normally, for minor releases, compatability is maintained. So, for example, chinook applications mostly work on diablo (two versions of Maemo 4). But there are no guarantees and, unusually, PR1.2 does break some libraries. Not all applications break, but some do. I must admit I am surprised to learn that libosso-abook breaks. I thought the breaks in PR1.2 were mainly Qt and possibly some obscure libs no one ever used! If I were in this position, I would continue to develop using the PR1.1 SDK, and submit sources to the autobuilder to build PR1.2 versions in extras-devel. That way I have both versions on hand. Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Failed to upload package through dput
Hi , I would like to upload my OSS project to maemo . However, I never can make it work with dput. The output of dput command is dput -f fremantle-extras-builder penpen_0.2-1_armel.changes Uploading to fremantle-extras-builder (via scp to drop.maemo.org): This is a restricted account. Warning: The execution of '/usr/bin/scp' as 'scp -p /home/benlau/src/buildarea/penpen_0.2-1.dsc /home/benlau/src/buildarea/penpen_0.2-1.tar.gz /home/benlau/src/buildarea/penpen_0.2-1_armel.deb /home/benlau/src/buildarea/penpen_0.2-1_armel.changes ben...@drop.maemo.org:/var/www/extras-devel/incoming-builder/fremantle' returned a nonzero exit code. Error while uploading. As I can ssh to drop.maemo.org , my ssh key should be set correctly. [sbox-FREMANTLE_ARMEL: ~] ssh ben...@drop.maemo.org [:snipped] Last login: Tue Jun 22 15:51:37 2010 from 221.125.8.44 This is a restricted account. You cannot execute anything here. Not enough arguments. Goodbye. Connection to drop.maemo.org closed. Anyone has idea about what is wrong with it? Moreover, I found that sometimes it will said Permission denied (publickey).. It happens randomly... p.s I have attached my dput.cf and result of `scp -v ` dput.cf Description: Binary data Executing: program /scratchbox/tools/bin/ssh host drop.maemo.org, user benlau, command scp -v -p -d -t /var/www/extras-devel/incoming-builder/fremantle OpenSSH_3.8.1p1, OpenSSL 0.9.7e 25 Oct 2004 debug1: Connecting to drop.maemo.org [80.248.164.251] port 22. debug1: Connection established. debug1: identity file /home/benlau/.ssh/identity type -1 debug1: identity file /home/benlau/.ssh/id_rsa type 1 debug1: identity file /home/benlau/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5 debug1: match: OpenSSH_5.1p1 Debian-5 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.8.1p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server-client aes128-cbc hmac-md5 none debug1: kex: client-server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'drop.maemo.org' is known and matches the RSA host key. debug1: Found key in /home/benlau/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/benlau/.ssh/identity debug1: Offering public key: /home/benlau/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 149 debug1: read PEM private key done: type RSA debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Entering interactive session. debug1: Sending command: scp -v -p -d -t /var/www/extras-devel/incoming-builder/fremantle debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: channel 0: free: client-session, nchannels 1 debug1: fd 0 clearing O_NONBLOCK debug1: fd 1 clearing O_NONBLOCK debug1: fd 2 clearing O_NONBLOCK debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.8 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 1 This is a restricted account. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Removing packages from Fremantle extras-devel
Hi guys, I'm looking for a procedure to remove packages uploaded in extras-devel. I read that there isn't actually a real way to do this and it can be operated only manually for us by maemo.org admin. For now, there is no nice package removal interface indeed. Can someone help me to remove sources that I had uploaded friday 11th in Fremantle extras-devel and related autobuilded packages? The name of source is dtn_2.7.0maemo-fremantle7 (https://garage.maemo.org/builder/fremantle/dtn_2.7.0maemo-fremantle7/) and the packages to remove are: dtn_2.7.0maemo-fremantle7_i386.deb dtn_2.7.0maemo-fremantle7_armel.deb python-dtn_2.7.0maemo-fremantle7_all.deb I have just uploaded a new version of my dtn implementation (version 8) that works correctly. The real problem is python-dtn that dosn't work properly and I remove it from version 8 compilation. python-dtn so I do not want to appear in packages list. I removed python-dtn. The other packages are not really a problem as version 8 replaces them anyway. Thanks in advantages! Thanks, Francesco Baldassarri -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Removing packages from Fremantle extras-devel
Thanks so much Niels Brett, but mmm I think that the package has been re-imported: Package imported System 2010-06-22 13:41 UTC Package has been removed System 2010-06-22 13:17 UTC Is normal? Thanks, Francesco Baldassarri Il giorno 22/giu/2010, alle ore 15.36, Niels Breet ha scritto: Hi guys, I'm looking for a procedure to remove packages uploaded in extras-devel. I read that there isn't actually a real way to do this and it can be operated only manually for us by maemo.org admin. For now, there is no nice package removal interface indeed. Can someone help me to remove sources that I had uploaded friday 11th in Fremantle extras-devel and related autobuilded packages? The name of source is dtn_2.7.0maemo-fremantle7 (https://garage.maemo.org/builder/fremantle/dtn_2.7.0maemo-fremantle7/) and the packages to remove are: dtn_2.7.0maemo-fremantle7_i386.deb dtn_2.7.0maemo-fremantle7_armel.deb python-dtn_2.7.0maemo-fremantle7_all.deb I have just uploaded a new version of my dtn implementation (version 8) that works correctly. The real problem is python-dtn that dosn't work properly and I remove it from version 8 compilation. python-dtn so I do not want to appear in packages list. I removed python-dtn. The other packages are not really a problem as version 8 replaces them anyway. Thanks in advantages! Thanks, Francesco Baldassarri -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
NokiaSDK (with latest updates): error compiling a QtMobility application for Maemo target
Hi all, I've upgraded Nokia SDK today and lot fo packages now are 1.0.0 or 2.0.0 so they should be almost the final release. I tried to compile a QtMobility application I'm working on and I can say I've no problem with Simulator: I can compile for this target and run my application on it without any problem. I get compilation errors when I try to compile it for Maemo target, in particular: Packaging Error: Could not copy '/home/andrea/Documents/sviluppo/msoma-build-n900/msoma' to '/home/andrea/Documents/sviluppo/msoma-build-n900/debian/msoma//usr/local/bin/msoma'. Error while building project msoma (target: Maemo) Here you can see the complete compilation logs: http://pastebin.com/p2Qw8P3X As you can read it looks like the application is compiled but at the end QtCreator try to deploy it somewhere, resulting in this error. Why does QtCreator try to deploy it? I aske it to Build not to Run it on the device. How can I fix this? Thanks for your help. -- Andrea Grandi email: a.grandi [AT] gmail [DOT] com website: http://www.andreagrandi.it PGP Key: http://www.andreagrandi.it/pgp_key.asc ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: NokiaSDK (with latest updates): error compiling a QtMobility application for Maemo target
Hi, Andrea. I've had the same issue for a while and I've opened a bug report for it: http://bugreports.qt.nokia.com/browse/QTCREATORBUG-1614 In my case, the error occurs only when building projects of template type 'SUBDIRS' for maemo using the QtCreator. If this is also your case, then I'm sorry say that currently, non-Desktop builds of 'SUBDIRS' projects are not supported as it says on the end of the bug report. On Tue, Jun 22, 2010 at 12:43 PM, Andrea Grandi a.gra...@gmail.com wrote: Hi all, I've upgraded Nokia SDK today and lot fo packages now are 1.0.0 or 2.0.0 so they should be almost the final release. I tried to compile a QtMobility application I'm working on and I can say I've no problem with Simulator: I can compile for this target and run my application on it without any problem. I get compilation errors when I try to compile it for Maemo target, in particular: Packaging Error: Could not copy '/home/andrea/Documents/sviluppo/msoma-build-n900/msoma' to '/home/andrea/Documents/sviluppo/msoma-build-n900/debian/msoma//usr/local/bin/msoma'. Error while building project msoma (target: Maemo) Here you can see the complete compilation logs: http://pastebin.com/p2Qw8P3X As you can read it looks like the application is compiled but at the end QtCreator try to deploy it somewhere, resulting in this error. Why does QtCreator try to deploy it? I aske it to Build not to Run it on the device. How can I fix this? Thanks for your help. -- Andrea Grandi email: a.grandi [AT] gmail [DOT] com website: http://www.andreagrandi.it PGP Key: http://www.andreagrandi.it/pgp_key.asc ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- Frederico Simas Duarte SW UI - Software and User Interface INDT - Nokia Institute http://fredyduarte.net/blog/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Command line to change master volume (N810)
Hi, I've been searching around to find a command (dbus most likely) to change the master volume. I've found one for N900 (using MAFW), but not for N810. Does anyone know if it is possible? Thanks, dc101x ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
