date:20091022

2009/10/22 Kamen Bundev bun...@gmail.com:
 Hmm, yes, that seems to be the problem. In the final SDK /opt is a symlink
 but in the latest beta SDK it is not. I didn't upgrade my development
 machine, but I have the final on another so I can compare. I'll report back
 if successful.

You're right.
Autobuilder uses latest SDK and /opt is in the rootstrap:
tar -ztf /scratchbox/packages/maemo-sdk-rootstrap_5.0_armel.tgz | grep '^\./opt'
./opt

I removed it from there and now packages with /opt directory should be
installable.
Try to re-upload your packages to autobuilder. It should work now.

Thank you for your help.

PS: Is someone willing to file a bug for SDK :) ?

-- 
BR,
Ed
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Maemo-Optify Builder Bots = Broken?

Hi,

Please read my last message. The issue is fixed. Nobody should do
anything except of SDK guys.

2009/10/22 Kamen Bundev bun...@gmail.com:
 Hi guys,

 I've played around with maemo-optify yesterday and decided to instead of
 creating the paths in the package subdir, to create a symlink to /opt and
 drop everything there before packaging. Wrong move, dpkg-deb doesn't follow
 symlinks, it packages them :) So, the logical step was to instead of symlink
 to /opt, to create home/opt in the package subdir and symlink opt/ to it.
 That worked and I have a package ready that will work in the device, but I'm
 hesitant to try it in the autobuilder because if the autobuilder is like
 scratchbox, then the package will be installed to /home/opt but the /opt
 symlinks will point to somewhere else (/targets/links/opt) and the build
 will fail anyway.

 So my question is - is this the right way to go about this and can I control
 where the /opt dir is symlinked to in the autobuilder?

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 2:35 AM, Nathan Anderson nat...@andersonsplace.net
 wrote:

 Kamen,

 I build both binary target and source targets debs in my scratchbox
 before I upload.For instance last night I had to rebuild the binary debs
 about 20 times (trying to get a weird make file rule to work).  Once I got
 it working then I would copy my rules to a fresh copy and re-run a source
 deb then re-run a binary once more just to make sure it wasn't left over
 stuff causing a success.  ;-)

So, I don't think it has anything to do with the scratchbox.  I suspect
 it as Ed found something to do with the symlink - directory or something in
 their on the auto-builder.

 Nathan.
 
 From: Kamen Bundev [mailto:bun...@gmail.com]
 Sent: Wednesday, October 21, 2009 6:14 PM
 To: Nathan Anderson
 Cc: maemo-developers@maemo.org
 Subject: Re: Maemo-Optify  Builder Bots = Broken?

 Nah, that's not enough. Still fails.

 Another difference is that I'm building my optified package in scratchbox
 before upload and the other people are using the autobuilder, so the problem
 should be somewhere else.

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 2:09 AM, Kamen Bundev bun...@gmail.com wrote:

 Nah, that's not enough. Still fails.

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev bun...@gmail.com wrote:

 Looks like the only difference here is that my /opt should be pointing
 to /targets/links/opt which is symlinked to the proper target on target
 change. Uploading the new package to extras now.

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 12:39 AM, Nathan Anderson
 nat...@andersonsplace.net wrote:

 Ed,

I believe this is what you are asking:
 FREMANTLE_ARMEL  cs2007q3-glibc2.5-arm7
 FREMANTLE_X86cs2007q3-glibc2.5-i486


 Nathan

 -Original Message-
 From: Ed Bartosh [mailto:bart...@gmail.com]
 Sent: Wednesday, October 21, 2009 4:03 PM
 To: Nathan Anderson
 Cc: maemo-developers@maemo.org
 Subject: Re: Maemo-Optify  Builder Bots = Broken?

 2009/10/21 Nathan Anderson nat...@andersonsplace.net:
  Ed,
 
 Sure can (and following the chain).
 
  ls -l / | grep opt
 lrwxrwxrwx1 root  root  18 Oct  6 22:36 opt -
  /targets/links/opt
 
  ls -l /targets/links/ | grep opt
 lrwxrwxrwx  1 maemo 1000 26 Oct 19 16:55 opt -
  /targets/FREMANTLE_X86/opt
 
 I've found the difference!
 In your environment /targets/target/opt is a directory. In
 autobuilder
 environment it's a symlink:

  ls -l /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/
  |grep opt
 lrwxrwxrwx   1 builder1 builder19 Oct 21 23:50 opt - /home/opt

 And it looks like it becomes symlink after rootstrap unpacking. Look:
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  sb-conf
 re
 -f
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  ls -l
 /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt
 drwxrwxr-x  2 1005 1006 4096 Oct 21 23:56 opt
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  sb-conf
 in
 --etc --devkits
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  ls -l
 /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt
 drwxrwxr-x   2 builder1 builder1 4096 Oct 21 23:56 opt
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  sb-conf
 in
 --fakeroot Installing fakeroot version 1.4.2.1...
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  ls -l
 /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt
 drwxrwxr-x   2 builder1 builder1 4096 Oct 21 23:56 opt
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  sb-conf
 rs
 /scratchbox/packages/maemo-sdk-rootstrap_5.0_armel.tgz
 Unpacking rootstrap...
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  ls -l
 /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt
 lrwxrwxrwx   1 1005 10069 Oct 21 23:57 opt - /home/opt

 So, the difference

Re: Maemo-Optify Builder Bots = Broken?

2009-10-22 Thread Kamen Bundev

Yup, just read it :) Thanks.

Regards:
Bundyo

On Thu, Oct 22, 2009 at 9:38 AM, Ed Bartosh bart...@gmail.com wrote:

 Hi,

 Please read my last message. The issue is fixed. Nobody should do
 anything except of SDK guys.

 2009/10/22 Kamen Bundev bun...@gmail.com:
  Hi guys,
 
  I've played around with maemo-optify yesterday and decided to instead of
  creating the paths in the package subdir, to create a symlink to /opt and
  drop everything there before packaging. Wrong move, dpkg-deb doesn't
 follow
  symlinks, it packages them :) So, the logical step was to instead of
 symlink
  to /opt, to create home/opt in the package subdir and symlink opt/ to it.
  That worked and I have a package ready that will work in the device, but
 I'm
  hesitant to try it in the autobuilder because if the autobuilder is like
  scratchbox, then the package will be installed to /home/opt but the /opt
  symlinks will point to somewhere else (/targets/links/opt) and the build
  will fail anyway.
 
  So my question is - is this the right way to go about this and can I
 control
  where the /opt dir is symlinked to in the autobuilder?
 
  Regards:
  Bundyo
 
  On Thu, Oct 22, 2009 at 2:35 AM, Nathan Anderson 
 nat...@andersonsplace.net
  wrote:
 
  Kamen,
 
  I build both binary target and source targets debs in my scratchbox
  before I upload.For instance last night I had to rebuild the binary
 debs
  about 20 times (trying to get a weird make file rule to work).  Once I
 got
  it working then I would copy my rules to a fresh copy and re-run a
 source
  deb then re-run a binary once more just to make sure it wasn't left
 over
  stuff causing a success.  ;-)
 
 So, I don't think it has anything to do with the scratchbox.  I
 suspect
  it as Ed found something to do with the symlink - directory or
 something in
  their on the auto-builder.
 
  Nathan.
  
  From: Kamen Bundev [mailto:bun...@gmail.com]
  Sent: Wednesday, October 21, 2009 6:14 PM
  To: Nathan Anderson
  Cc: maemo-developers@maemo.org
  Subject: Re: Maemo-Optify  Builder Bots = Broken?
 
  Nah, that's not enough. Still fails.
 
  Another difference is that I'm building my optified package in
 scratchbox
  before upload and the other people are using the autobuilder, so the
 problem
  should be somewhere else.
 
  Regards:
  Bundyo
 
  On Thu, Oct 22, 2009 at 2:09 AM, Kamen Bundev bun...@gmail.com wrote:
 
  Nah, that's not enough. Still fails.
 
  Regards:
  Bundyo
 
  On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev bun...@gmail.com
 wrote:
 
  Looks like the only difference here is that my /opt should be pointing
  to /targets/links/opt which is symlinked to the proper target on
 target
  change. Uploading the new package to extras now.
 
  Regards:
  Bundyo
 
  On Thu, Oct 22, 2009 at 12:39 AM, Nathan Anderson
  nat...@andersonsplace.net wrote:
 
  Ed,
 
 I believe this is what you are asking:
  FREMANTLE_ARMEL  cs2007q3-glibc2.5-arm7
  FREMANTLE_X86cs2007q3-glibc2.5-i486
 
 
  Nathan
 
  -Original Message-
  From: Ed Bartosh [mailto:bart...@gmail.com]
  Sent: Wednesday, October 21, 2009 4:03 PM
  To: Nathan Anderson
  Cc: maemo-developers@maemo.org
  Subject: Re: Maemo-Optify  Builder Bots = Broken?
 
  2009/10/21 Nathan Anderson nat...@andersonsplace.net:
   Ed,
  
  Sure can (and following the chain).
  
   ls -l / | grep opt
  lrwxrwxrwx1 root  root  18 Oct  6 22:36 opt -
   /targets/links/opt
  
   ls -l /targets/links/ | grep opt
  lrwxrwxrwx  1 maemo 1000 26 Oct 19 16:55 opt -
   /targets/FREMANTLE_X86/opt
  
  I've found the difference!
  In your environment /targets/target/opt is a directory. In
  autobuilder
  environment it's a symlink:
 
   ls -l /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/
   |grep opt
  lrwxrwxrwx   1 builder1 builder19 Oct 21 23:50 opt - /home/opt
 
  And it looks like it becomes symlink after rootstrap unpacking. Look:
  [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] 
 sb-conf
  re
  -f
  [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  ls -l
  /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep
 opt
  drwxrwxr-x  2 1005 1006 4096 Oct 21 23:56 opt
  [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] 
 sb-conf
  in
  --etc --devkits
  [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  ls -l
  /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep
 opt
  drwxrwxr-x   2 builder1 builder1 4096 Oct 21 23:56 opt
  [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] 
 sb-conf
  in
  --fakeroot Installing fakeroot version 1.4.2.1...
  [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  ls -l
  /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep
 opt
  drwxrwxr-x   2 builder1 builder1 4096 Oct 21 23:56 opt
  [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~] 
 sb-conf
  rs

Re: Considering /opt and MyDocs in your packages

2009-10-22 Thread Martin Grimme

Hi,

 It would be helpful if you could provide instructions on how to install
 apps directly into /opt without changing too much of the packaging
 stuff (remember, some package maintainers have to keep the Diablo
 version and maybe even a Linux Desktop version up to date as well,
 so anything that avoids big differences in packaging/code helps here).

This depends on how you have setup your build-system. With GNU
autotools, running configure.sh with --prefix=/opt/packagename would
be a way, but you
have to take care that the application icon, .desktop file and D-Bus
service activation description still get into the rootfs.
If you're using a simple Makefile instead if autotools then you have
full control already.
Relocating Python apps to /opt should be pretty simple. I do so by
installing into /opt/packagename and putting a symlink to the
executable module into /usr/bin/ (although this is not really required
if the path in the D-Bus service activation description already points
to /opt). If I need to find out about the installation path of my
application, I read the __file__ variable which in every Python module
points to the file path of that module file, so I know where to find
my graphics and other data files, no matter where my application got
installed.
For C applications you may experience other problems such as not
finding .so files.
A way around this could be replacing the executable in /usr/bin with a
shell script setting up the LD_LIBRARY_PATH variable for your app
correctly. XDG_DATA_DIR can be specified by environment vatiables,
too, IIRC.

 I think a subsection on this wiki page would be ideal:

 http://wiki.maemo.org/Opt_Problem

I fully agree. Developers should be made aware that maemo-optify is
not always the best way to move stuff to /opt.
If I find some time this evening I'm going to make a start on the wiki page.
There are some more caveats I stumpled upon, e.g. putting application
graphics other than the app icon into /usr/share/icons results in a
huge icon cache file.
These issues should all be covered on the wiki page IMHO.


 Adding maemo-optify as build-depends and to debian/rules is just
 simpler and more straightforward than doing more intrusive changes.

Yes, nothing against it. But developers should be made aware of the
problems that may arise and that alternatives do exist. For porting
stuff with hardcoded paths optify might still be the only feasible
way, especially for developers without deep Linux experience.


Martin
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Maemo-Optify Builder Bots = Broken?

Hi,

I restarted Nathan's build and autobuilder seems to be able to install
all build-deps.
You can see autobuilder logs here soon:
https://garage.maemo.org/builder/fremantle/sword_1.6.0a-0maemo1/

2009/10/22 Ed Bartosh bart...@gmail.com:
 Hi,

 Please read my last message. The issue is fixed. Nobody should do
 anything except of SDK guys.

 2009/10/22 Kamen Bundev bun...@gmail.com:
 Hi guys,

 I've played around with maemo-optify yesterday and decided to instead of
 creating the paths in the package subdir, to create a symlink to /opt and
 drop everything there before packaging. Wrong move, dpkg-deb doesn't follow
 symlinks, it packages them :) So, the logical step was to instead of symlink
 to /opt, to create home/opt in the package subdir and symlink opt/ to it.
 That worked and I have a package ready that will work in the device, but I'm
 hesitant to try it in the autobuilder because if the autobuilder is like
 scratchbox, then the package will be installed to /home/opt but the /opt
 symlinks will point to somewhere else (/targets/links/opt) and the build
 will fail anyway.

 So my question is - is this the right way to go about this and can I control
 where the /opt dir is symlinked to in the autobuilder?

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 2:35 AM, Nathan Anderson nat...@andersonsplace.net
 wrote:

 Kamen,

 I build both binary target and source targets debs in my scratchbox
 before I upload.For instance last night I had to rebuild the binary debs
 about 20 times (trying to get a weird make file rule to work).  Once I got
 it working then I would copy my rules to a fresh copy and re-run a source
 deb then re-run a binary once more just to make sure it wasn't left over
 stuff causing a success.  ;-)

So, I don't think it has anything to do with the scratchbox.  I suspect
 it as Ed found something to do with the symlink - directory or something in
 their on the auto-builder.

 Nathan.
 
 From: Kamen Bundev [mailto:bun...@gmail.com]
 Sent: Wednesday, October 21, 2009 6:14 PM
 To: Nathan Anderson
 Cc: maemo-developers@maemo.org
 Subject: Re: Maemo-Optify  Builder Bots = Broken?

 Nah, that's not enough. Still fails.

 Another difference is that I'm building my optified package in scratchbox
 before upload and the other people are using the autobuilder, so the problem
 should be somewhere else.

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 2:09 AM, Kamen Bundev bun...@gmail.com wrote:

 Nah, that's not enough. Still fails.

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev bun...@gmail.com wrote:

 Looks like the only difference here is that my /opt should be pointing
 to /targets/links/opt which is symlinked to the proper target on target
 change. Uploading the new package to extras now.

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 12:39 AM, Nathan Anderson
 nat...@andersonsplace.net wrote:

 Ed,

I believe this is what you are asking:
 FREMANTLE_ARMEL  cs2007q3-glibc2.5-arm7
 FREMANTLE_X86cs2007q3-glibc2.5-i486


 Nathan

 -Original Message-
 From: Ed Bartosh [mailto:bart...@gmail.com]
 Sent: Wednesday, October 21, 2009 4:03 PM
 To: Nathan Anderson
 Cc: maemo-developers@maemo.org
 Subject: Re: Maemo-Optify  Builder Bots = Broken?

 2009/10/21 Nathan Anderson nat...@andersonsplace.net:
  Ed,
 
 Sure can (and following the chain).
 
  ls -l / | grep opt
 lrwxrwxrwx1 root  root  18 Oct  6 22:36 opt -
  /targets/links/opt
 
  ls -l /targets/links/ | grep opt
 lrwxrwxrwx  1 maemo 1000 26 Oct 19 16:55 opt -
  /targets/FREMANTLE_X86/opt
 
 I've found the difference!
 In your environment /targets/target/opt is a directory. In
 autobuilder
 environment it's a symlink:

  ls -l /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/
  |grep opt
 lrwxrwxrwx   1 builder1 builder19 Oct 21 23:50 opt - /home/opt

 And it looks like it becomes symlink after rootstrap unpacking. Look:
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  sb-conf
 re
 -f
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  ls -l
 /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt
 drwxrwxr-x  2 1005 1006 4096 Oct 21 23:56 opt
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  sb-conf
 in
 --etc --devkits
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  ls -l
 /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt
 drwxrwxr-x   2 builder1 builder1 4096 Oct 21 23:56 opt
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  sb-conf
 in
 --fakeroot Installing fakeroot version 1.4.2.1...
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  ls -l
 /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ |grep opt
 drwxrwxr-x   2 builder1 builder1 4096 Oct 21 23:56 opt
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  sb-conf
 rs
 /scratchbox/packages/maemo-sdk-rootstrap_5.0_armel.tgz

Re: Maemo-Optify Builder Bots = Broken?

2009-10-22 Thread Marius Vollmer

ext Ed Bartosh bart...@gmail.com writes:

 2009/10/22 Kamen Bundev bun...@gmail.com:
 Hmm, yes, that seems to be the problem. In the final SDK /opt is a symlink
 but in the latest beta SDK it is not. I didn't upgrade my development
 machine, but I have the final on another so I can compare. I'll report back
 if successful.

 You're right.
 Autobuilder uses latest SDK and /opt is in the rootstrap:
 tar -ztf /scratchbox/packages/maemo-sdk-rootstrap_5.0_armel.tgz | grep 
 '^\./opt'
 ./opt

 I removed it from there and now packages with /opt directory should be
 installable.  Try to re-upload your packages to autobuilder. It should
 work now.

 Thank you for your help.

 PS: Is someone willing to file a bug for SDK :) ?

I can do that.

Thanks a lot Ed!
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

SyncEvolution in Fremantle

2009-10-22 Thread Patrick Ohly

Hello Maemo!

It has been a while that I posted anything here. Ironically, since I
started working on SyncEvolution full-time beginning of this year, I
seem to have *less* time left compared to the previous years when I did
it in my spare time ;-)

For those who haven't heard about it:
* SyncEvolution is a SyncML client synchronizing PIM data with
SyncML servers [1]. The versions = 0.8.1 are available for
Maemo [2] and work with the builtin address book and the Dates
calendar.
* This year it became the sync solution in Moblin and switched to
the Synthesis SyncML engine [3], with the goal of using that
also as SyncML server on a desktop [4].
* We have direct client to server synchronization working in the
development branch, without depending on closed third party
software [5].

I'd love to see the latest SyncEvolution releases packaged properly for
Maemo, and so do users [6]. 0.8.1 still works fine on the older Maemo
releases it is available for, but 0.9 has several relevant improvements,
for example synchronization with Google Contacts and a GTK GUI.

I'm posting here because I hope that an interested developer or
maintainer will step up and take over packaging for Maemo. You can be
sure that this will have full support when it comes to merging patches
and including the Maemo port as first-class citizen in releases.

Another interesting area to work on would be support for other local
databases. GPE has been asked for several times. There is a plugable
backend API which would allow that, if a developer is interested [7].
That article is a bit dated, but still relevant. 0.9.1 (about to be
released) has several improvements that make writing a backend simpler,
for example it is not necessary to have your own
vCard/iCalendar/vCalendar encoder/decoder. Instead, it is possible to
exchange properties directly with the internal Synthesis format [8]. The
sqlite backend demonstrates that. For an introduction to the Synthesis
engine see [9].

I'm cross-posting to the SyncEvolution list to keep the other
SyncEvolution developers informed. If there's anything that I can help
with, please don't hesitate to reply here or contact me directly.

[1] http://syncevolution.org
[2] http://maemo.org/downloads/product/OS2008/syncevolution/
[3]
http://www.estamos.de/blog/2009/05/13/syncevolution-09-beta-1-full-time-project-using-synthesis-syncml-engine/
[4]
http://syncevolution.org/development/direct-synchronization-aka-syncml-server
[5] http://article.gmane.org/gmane.comp.mobile.syncevolution/434
[6] http://talk.maemo.org/showthread.php?t=32515
[7] http://www.estamos.de/blog/2008/08/04/syncml-client-do-it-yourself-style/
[8] http://article.gmane.org/gmane.comp.mobile.syncevolution/136
[9] http://syncevolution.org/development/pim-data-synchronization-why-it-so-hard

--
Bye, Patrick Ohly
--
patrick.o...@gmx.de
http://www.estamos.de/

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Changing Freemantle Desktop Backgrounds

2009-10-22 Thread Andrea Borgia

Andrea Grandi ha scritto:


 2009/10/22 Kimmo Hämäläinen kimmo.hamalai...@nokia.com:
 On Thu, 2009-10-22 at 01:36 +0200, ext Jonathan Blake wrote:
 First post here, so greetings, etc. :)
 First things first, it's Fremantle, the code names come from a list of
 winds:
 http://en.wikipedia.org/wiki/List_of_local_winds
 
 wow! really didn't know :)
 let's try to guess the codename that will follow Harmattan ;)

More importantly ;-) I don't see Diablo in that list, although that is
also a wind:
http://en.wikipedia.org/wiki/Diablo_wind

A.

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

external control of phone application?

2009-10-22 Thread Andrea Borgia

Hi, guys.

I am looking for a way to receive notifications of incoming calls /
messages and to tell the phone application how to react based on some
arbitrary criteria.

I've found the APIs for tying into the address book but I am a bit lost
when it comes to the phone application.

Any pointers? Or put-downs? ^^;

A.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Full Screen Hotkey?

2009-10-22 Thread Cornelius Hald

ds wrote:
 What about pressing + and - at the same time? At least if I remember
 correctly the N800 was able to signalize this. If + and - are beside
 each other on N900 this might be comparable to the place where N800 had
 the button (between + and -)

The N900 hardware does not allow that. The button is build in a way that 
you can press + or -, not both at the same time.

Personally I think I like Ctrl+Space and I don´t know any application 
which is using it already. I didn´t do extensive checks, though :)

Cheers!
Conny
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Changing Freemantle Desktop Backgrounds

2009-10-22 Thread Thomas Waelti

And because it is a wiki, I just changed it.
HINT: you can do similar things in the maemo.org wiki...  ;-)
-Tom

(sorry for slightly OT, but the Wiki Action Group needs to push the Wiki :-)


 Andrea Grandi ha scritto:

 More importantly ;-) I don't see Diablo in that list, although that is
 also a wind:
 http://en.wikipedia.org/wiki/Diablo_wind

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Using the sharing plugins

Hi,

I've seen the documentation about how to make your own sharing plugin [1].

Is there documentation on how to actually use them from our own application?

[1] 
http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Using_Data_Sharing/Sharing_Plug-in

--
anidel
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: SyncEvolution in Fremantle

2009-10-22 Thread Yves-Alexis Perez

Patrick Ohly a écrit :
 Hello Maemo!
 
 It has been a while that I posted anything here. Ironically, since I
 started working on SyncEvolution full-time beginning of this year, I
 seem to have *less* time left compared to the previous years when I did
 it in my spare time ;-)
 
 For those who haven't heard about it:
   * SyncEvolution is a SyncML client synchronizing PIM data with
 SyncML servers [1]. The versions = 0.8.1 are available for
 Maemo [2] and work with the builtin address book and the Dates
 calendar.
   * This year it became the sync solution in Moblin and switched to
 the Synthesis SyncML engine [3], with the goal of using that
 also as SyncML server on a desktop [4].
   * We have direct client to server synchronization working in the
 development branch, without depending on closed third party
 software [5].
 
 I'd love to see the latest SyncEvolution releases packaged properly for
 Maemo, and so do users [6]. 0.8.1 still works fine on the older Maemo
 releases it is available for, but 0.9 has several relevant improvements,
 for example synchronization with Google Contacts and a GTK GUI.
 
 I'm posting here because I hope that an interested developer or
 maintainer will step up and take over packaging for Maemo. You can be
 sure that this will have full support when it comes to merging patches
 and including the Maemo port as first-class citizen in releases.
 
Eh, funny, I just posted yet another thread on talk
(http://talk.maemo.org/showthread.php?t=33308)

The syncevolution and libsynthesis packages have recently been uploaded
to Debian (I sponsored them) and I would really be interested to be able
to use them on both laptop and n900 (when I have one). So yeah, at one
point I may give a hand for that to happen.

Does the to-be-release 0.9.1 will do the direct sync without third party
syncML servers?

Cheers,

-- 
Yves-Alexis
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: maemo.org/packages not identifying new version correctly?

2009-10-22 Thread Niels Breet

Hi,
On Wed, October 21, 2009 17:28, David King wrote:
 I uploaded glom 1.12.2-0maemo2 to extras-devel yesterday evening, which
 built fine. However, looking at:

 http://maemo.org/packages/package_instance/view/fremantle_extras-devel_fr
 ee_armel/glom/1.12.2-0maemo2/

 I see that an old version 1.12.2-0maemo1 is in the File field. There is
 also a dependency warning, that is not present in the 1.12.2-0maemo2
 version (which I uploaded to fix exactly this problem). I can install
 1.12.2-0maemo2 on an N900, so the dependency problem does not seem to
 be an issue, but maybe the package description is somehow stale?


You spotted a bug in the package importer. I have now fixed that bug, so
it should look a lot better for you now?

Thanks for reporting!

 --
 David King | http://amigadave.blogspot.com/ | dav...@openismus.com

--
Niels Breet
maemo.org webmaster


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: SyncEvolution in Fremantle

2009-10-22 Thread Patrick Ohly

On Thu, 2009-10-22 at 11:22 +0200, Yves-Alexis Perez wrote:
 Patrick Ohly a écrit :
  I'm posting here because I hope that an interested developer or
  maintainer will step up and take over packaging for Maemo. You can be
  sure that this will have full support when it comes to merging patches
  and including the Maemo port as first-class citizen in releases.
  
 Eh, funny, I just posted yet another thread on talk
 (http://talk.maemo.org/showthread.php?t=33308)
 
 The syncevolution and libsynthesis packages have recently been uploaded
 to Debian (I sponsored them) and I would really be interested to be able
 to use them on both laptop and n900 (when I have one). So yeah, at one
 point I may give a hand for that to happen.
 
 Does the to-be-release 0.9.1 will do the direct sync without third party
 syncML servers?

No, 0.9.1 adds some new features and bug fixes:
http://syncevolution.org/blogs/pohly/2009/syncevolution-091-beta-released

The direct sync will come in 1.0, in one way or another. There's still a
lot of work left to do. On the development branch it is working, with
known issues and manual configuration. Once we solve the known issues,
we still need to figure out how to automate the setup and make it easier
to use.

-- 
Bye, Patrick Ohly
--  
patrick.o...@gmx.de
http://www.estamos.de/


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Announcement: mafw-gst-eq-renderer initial version

2009-10-22 Thread Juan A. Suarez Romero

Hi maemoers!

After reading some complaints about lack of an equalizer in N900, I've
written a replacement for mafw-gst-renderer called mafw-gst-eq-renderer.
It is not part of official MAFW.

Roughly speaking, it is mafw-gst-renderer with a gstreamer's 10-band
equalizer.

There are two flavours: one intended to replace current
mafw-gst-renderer, and another one intended to coexist with the original
renderer.

If you choose the second flavour, default mediaplayer will not be able
to use it, as it only handles one renderer: mafw-gst-renderer.

Both flavours come with a Control Panel applet that allows to set
equalizer values, and with a set of typical presets (though you can save
your own presets).


More information here:
http://blogs.igalia.com/jasuarez/2009/10/21/mafw-renderer-plugin-with-equalizer/


J.A.

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

can't install application to phone from local repository

2009-10-22 Thread ibrahim

cheers;

I created a local repository to host some test applications for Maemo 
fremantle device - and YES, the repository folders are visible to the 
phone- Added some packages and ran the dpkg-scanpackages utility to 
generate the Package  and Package.gz files with no errors.

_the contents of the Package file :_

Package: hello
Version: 1.0
Architecture: all
Maintainer: Your Name y...@email.com mailto:y...@email.com
Filename: hello-1.0.deb
Size: 4158
MD5sum: ce9ebc5398438693ae49d1f7c7679633
Section: base
Priority: optional
Description: Hello World When you need some sunshine, just run this 
small program!

 

the directory structure of my local repository is : 
/var/www/repo/dists/fremantle/free/binary-armel/
so, the url to the package files is :
http://local-ip/repo/dists/fremantle/free/binary-armel/ 
http://%3clocal-ip%3e/repo/dists/fremantle/free/binary-armel/

application packages and the index files Package files are inside the 
binary-armel/ folder

_ the .install file for the application :_

[install]
catalogues= hellocat
package= hello

[hellocat]
name = hello
uri= http://local-ip/repo http://%3clocal-ip%3e/repo
dist= fremantle
components = free

 

opening the install file on the device with the Application Manager adds 
the catalogue to the catalogues list, the installation procedure starts 
saying:preparing for the installation, please wait
 but the Application manager says that it couldn't download the 
application : unable to download 'hello'. Application package not found.
Yet, the Application Manager's log doesn't show any error at all

the catalogue entry is added to the sources file 
/etc/apt/sources.list.d/hildon-application-manager.list as follows:
deb http://local-ip/repo http://%3clocal-ip%3e/repo fremantle free

I tried to download the application from the Xterminal application - 
using the gainroot program:
apt-get install hello
And surprisingly, the application manages to download and install !
the question is : What is wrong with the way i deployed the application 
that the Application Manager refuses to install it, yet it is downloaded 
from the command line ? Am i missing something?

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

extras-testing QA checklist (proposal)

2009-10-22 Thread Quim Gil

http://wiki.maemo.org/Extras-testing/QA_Checklist

Feedback please. This checklist is common for developers (before
promnoting their applications to extras-testing) and betatesters (before
giving them farewell to reach Extras).

It would be good to have more specific instructions to measure
performace and power management, since sometimes the problems are not
obvious specially in only one session or even a couple of days of casual
testing.

This has been posted at http://talk.maemo.org/showthread.php?p=355270 as
well.

-- 
Quim Gil
open source advocate
Maemo Devices @ Nokia
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: can't install application to phone from local repository

2009-10-22 Thread Marius Gedminas

On Thu, Oct 22, 2009 at 02:04:38PM +0200, ibrahim wrote:
 Package: hello
...
 Section: base
...
  but the Application manager says that it couldn't download the 
 application : unable to download 'hello'. Application package not found.

The Application Manager lets the user install only those packages that
are in sections starting with user/.  It installs packages from other
sections only as dependencies for user/* packages.

The list of supported sections is in the wiki:
http://wiki.maemo.org/Maemo_packaging#Sections

HTH,
Marius Gedminas
-- 
Linux became only possible because 20 years of OS research was carefully
studied, analyzed, discussed and thrown away.
-- Ingo Molnar


signature.asc
Description: Digital signature
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

QA queue determine required thumbs down for removal

2009-10-22 Thread Niels Breet

Hi,

To not keep obvious broken applications lingering in the QA testing queue,
we need to determine what how many thumbs down are required before
automatic removal from the queue is done.

How about setting the limit at:

5 thumbs down at = 10 day quarantine point.
and
10 thumbs down for immediate removal.

Another thing to think about is if we only want to remove the package from
the QA queue or also remove it from the extras-testing repository.

Thoughts?

--
Niels Breet
maemo.org webmaster


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: QA queue determine required thumbs down for removal

2009/10/22 Niels Breet ni...@maemo.org:
 Hi,

 To not keep obvious broken applications lingering in the QA testing queue,
 we need to determine what how many thumbs down are required before
 automatic removal from the queue is done.

 How about setting the limit at:

 5 thumbs down at = 10 day quarantine point.
 and
 10 thumbs down for immediate removal.

 Another thing to think about is if we only want to remove the package from
 the QA queue or also remove it from the extras-testing repository.

 Thoughts?

We could remove it from Extras Testing after another 10 days in quarantine
(as it means 20 days the developer hasn't done anything on it)

The numbers you're stating are relative or absolute?

I.e. 10 thumbs up - 7 thumbs down = 3 thumbs up and after the 10 days
go to quarantine?

--
anidel
Sent from London, Eng, United Kingdom
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: extras-testing QA checklist (proposal)

2009-10-22 Thread Andrew Flegg

On Thu, Oct 22, 2009 at 13:31, Quim Gil quim@nokia.com wrote:
 http://wiki.maemo.org/Extras-testing/QA_Checklist

 Feedback please. This checklist is common for developers (before
 promnoting their applications to extras-testing) and betatesters (before
 giving them farewell to reach Extras).

The first half doesn't seem to be a checklist - but an introduction to
Extras Testing. Testers (and developers) should have short bullet
points - perhaps even a table?

It does seem to be a good document for an *introduction* to QA 
testing, but I wouldn't say it was the checklist itself. Does that
make sense?

Cheers,

Andrew

-- 
Andrew Flegg -- mailto:and...@bleb.org  |  http://www.bleb.org/
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: QA queue determine required thumbs down for removal

2009-10-22 Thread gary liquid

There is no interface to pull apps manually.
if testing identifies a blocker, the maintainer has no way but to leave it
there wasting the other testers time.


On Thu, Oct 22, 2009 at 12:56 PM, Aniello Del Sorbo ani...@gmail.comwrote:

 2009/10/22 Niels Breet ni...@maemo.org:
  Hi,
 
  To not keep obvious broken applications lingering in the QA testing
 queue,
  we need to determine what how many thumbs down are required before
  automatic removal from the queue is done.
 
  How about setting the limit at:
 
  5 thumbs down at = 10 day quarantine point.
  and
  10 thumbs down for immediate removal.
 
  Another thing to think about is if we only want to remove the package
 from
  the QA queue or also remove it from the extras-testing repository.
 
  Thoughts?

 We could remove it from Extras Testing after another 10 days in quarantine
 (as it means 20 days the developer hasn't done anything on it)

 The numbers you're stating are relative or absolute?

 I.e. 10 thumbs up - 7 thumbs down = 3 thumbs up and after the 10 days
 go to quarantine?

 --
 anidel
 Sent from London, Eng, United Kingdom
 ___
 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: QA queue determine required thumbs down for removal

This is a good point.

An app should be pulled by the developer or by some poweruser .

Aniello

2009/10/22 gary liquid liq...@gmail.com:

 There is no interface to pull apps manually.
 if testing identifies a blocker, the maintainer has no way but to leave it
 there wasting the other testers time.


 On Thu, Oct 22, 2009 at 12:56 PM, Aniello Del Sorbo ani...@gmail.com
 wrote:

 2009/10/22 Niels Breet ni...@maemo.org:
  Hi,
 
  To not keep obvious broken applications lingering in the QA testing
  queue,
  we need to determine what how many thumbs down are required before
  automatic removal from the queue is done.
 
  How about setting the limit at:
 
  5 thumbs down at = 10 day quarantine point.
  and
  10 thumbs down for immediate removal.
 
  Another thing to think about is if we only want to remove the package
  from
  the QA queue or also remove it from the extras-testing repository.
 
  Thoughts?

 We could remove it from Extras Testing after another 10 days in quarantine
 (as it means 20 days the developer hasn't done anything on it)

 The numbers you're stating are relative or absolute?

 I.e. 10 thumbs up - 7 thumbs down = 3 thumbs up and after the 10 days
 go to quarantine?

 --
 anidel
 Sent from London, Eng, United Kingdom
 ___
 maemo-developers mailing list
 maemo-developers@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-developers





-- 

--
anidel
Sent from London, Eng, United Kingdom
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

RE: Maemo-Optify Builder Bots = Broken?

2009-10-22 Thread Nathan Anderson

Ed,

Cool!   Thanks, I will upload my fixed dep package and I should be
good to go!

Nathan

-Original Message-
From: Ed Bartosh [mailto:bart...@gmail.com] 
Sent: Thursday, October 22, 2009 2:17 AM
To: Kamen Bundev
Cc: Nathan Anderson; maemo-developers@maemo.org
Subject: Re: Maemo-Optify  Builder Bots = Broken?

Hi,

I restarted Nathan's build and autobuilder seems to be able to install all
build-deps.
You can see autobuilder logs here soon:
https://garage.maemo.org/builder/fremantle/sword_1.6.0a-0maemo1/

2009/10/22 Ed Bartosh bart...@gmail.com:
 Hi,

 Please read my last message. The issue is fixed. Nobody should do 
 anything except of SDK guys.

 2009/10/22 Kamen Bundev bun...@gmail.com:
 Hi guys,

 I've played around with maemo-optify yesterday and decided to instead 
 of creating the paths in the package subdir, to create a symlink to 
 /opt and drop everything there before packaging. Wrong move, dpkg-deb 
 doesn't follow symlinks, it packages them :) So, the logical step was 
 to instead of symlink to /opt, to create home/opt in the package subdir
and symlink opt/ to it.
 That worked and I have a package ready that will work in the device, 
 but I'm hesitant to try it in the autobuilder because if the 
 autobuilder is like scratchbox, then the package will be installed to 
 /home/opt but the /opt symlinks will point to somewhere else 
 (/targets/links/opt) and the build will fail anyway.

 So my question is - is this the right way to go about this and can I 
 control where the /opt dir is symlinked to in the autobuilder?

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 2:35 AM, Nathan Anderson 
 nat...@andersonsplace.net
 wrote:

 Kamen,

 I build both binary target and source targets debs in my scratchbox
 before I upload.For instance last night I had to rebuild the binary
debs
 about 20 times (trying to get a weird make file rule to work).  Once 
 I got it working then I would copy my rules to a fresh copy and 
 re-run a source deb then re-run a binary once more just to make sure 
 it wasn't left over stuff causing a success.  ;-)

So, I don't think it has anything to do with the scratchbox.  I 
 suspect it as Ed found something to do with the symlink - directory 
 or something in their on the auto-builder.

 Nathan.
 
 From: Kamen Bundev [mailto:bun...@gmail.com]
 Sent: Wednesday, October 21, 2009 6:14 PM
 To: Nathan Anderson
 Cc: maemo-developers@maemo.org
 Subject: Re: Maemo-Optify  Builder Bots = Broken?

 Nah, that's not enough. Still fails.

 Another difference is that I'm building my optified package in 
 scratchbox before upload and the other people are using the 
 autobuilder, so the problem should be somewhere else.

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 2:09 AM, Kamen Bundev bun...@gmail.com wrote:

 Nah, that's not enough. Still fails.

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 12:52 AM, Kamen Bundev bun...@gmail.com
wrote:

 Looks like the only difference here is that my /opt should be 
 pointing to /targets/links/opt which is symlinked to the proper 
 target on target change. Uploading the new package to extras now.

 Regards:
 Bundyo

 On Thu, Oct 22, 2009 at 12:39 AM, Nathan Anderson 
 nat...@andersonsplace.net wrote:

 Ed,

I believe this is what you are asking:
 FREMANTLE_ARMEL  cs2007q3-glibc2.5-arm7
 FREMANTLE_X86cs2007q3-glibc2.5-i486


 Nathan

 -Original Message-
 From: Ed Bartosh [mailto:bart...@gmail.com]
 Sent: Wednesday, October 21, 2009 4:03 PM
 To: Nathan Anderson
 Cc: maemo-developers@maemo.org
 Subject: Re: Maemo-Optify  Builder Bots = Broken?

 2009/10/21 Nathan Anderson nat...@andersonsplace.net:
  Ed,
 
 Sure can (and following the chain).
 
  ls -l / | grep opt
 lrwxrwxrwx1 root  root  18 Oct  6 22:36 opt -
  /targets/links/opt
 
  ls -l /targets/links/ | grep opt
 lrwxrwxrwx  1 maemo 1000 26 Oct 19 16:55 opt - 
  /targets/FREMANTLE_X86/opt
 
 I've found the difference!
 In your environment /targets/target/opt is a directory. In 
 autobuilder environment it's a symlink:

  ls -l 
  /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/
  |grep opt
 lrwxrwxrwx   1 builder1 builder19 Oct 21 23:50 opt - /home/opt

 And it looks like it becomes symlink after rootstrap unpacking. Look:
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  
 sb-conf re -f
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  
 ls -l 
 /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/ 
 |grep opt drwxrwxr-x  2 1005 1006 4096 Oct 21 23:56 opt
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  
 sb-conf in --etc --devkits
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  
 ls -l /targets/maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c/
|grep opt
 drwxrwxr-x   2 builder1 builder1 4096 Oct 21 23:56 opt
 [sbox-maemo5-arm-183e1d1de998260fa89b870d65b22998c6908b6c: ~]  
 sb-conf in --fakeroot Installing

Re: QA queue determine required thumbs down for removal

2009-10-22 Thread Niels Breet

On Thu, October 22, 2009 15:31, gary liquid wrote:
 There is no interface to pull apps manually.
 if testing identifies a blocker, the maintainer has no way but to leave it
  there wasting the other testers time.

This reminds me. If a maintainer votes his own app down, it should be
removed instantly.

This way a maintainer can easily remove his own app and not waste testers'
time.

--
Niels Breet
maemo.org webmaster




___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: QA queue determine required thumbs down for removal

2009/10/22 Niels Breet ni...@maemo.org:
 On Thu, October 22, 2009 15:31, gary liquid wrote:
 There is no interface to pull apps manually.
 if testing identifies a blocker, the maintainer has no way but to leave it
  there wasting the other testers time.

 This reminds me. If a maintainer votes his own app down, it should be
 removed instantly.

 This way a maintainer can easily remove his own app and not waste testers'
 time.


/me likes that.

--
anidel
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Screenshot as loading screen on Maemo 5

On Sat, Oct 17, 2009 at 1:03 PM, Cornelius Hald h...@icandy.de wrote:

 On Sat, 2009-10-17 at 11:58 +0100, Aniello Del Sorbo wrote:
 
  My program doesn't ask anything when you close it, but it keeps
  automatically saving the document in
  a temporary file. Thus at every start it loads it up and you're back
  where you left.
  So I thought I would call the screenshot function at the very end,
  while closing down the program.
 
  It didn't work. It didn't save the screenshot of what was there.
 
  So I call it when I receive the expose event (like in the example) and
  it does work there.
  Why is that?
 
  I still have to investigate it, but I thought the window would be
  still available in my Quit function
  when called from the destroy event.

 I'm also calling it when quitting the application. I'm using the
 'delete-event' on my main window. There I call it just before
 gtk_main_quit(). It's working for me...

 Cheers!
 Conny


 ___
 maemo-developers mailing list
 maemo-developers@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-developers


I'm resuming an old thread, sorry!

If I call hildon_gtk_window_take_screenshot() within the callback function
for the delete-event of the main app, just before gtk_main_quit(), it seems
that something has already happened to the main window: it complains that it
is not a GtkWindow (which usually is, as HildonWindow derives from it), but
a GdkWindow, and, of course, no screenshot were taken.

Luca Donaggio
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Maemo.org/packages and bug tracker url

Is the proposed XSBC-Bugtracker field to specify an alternative bug tracker
used by the package interface at the moment?
I'm not using maemo bugzilla for my packages, but the garage provided bug
tracker instead and I would like that to be shown on maemo.org package
interface.

Luca Donaggio
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: QA queue determine required thumbs down for removal

On Thu, Oct 22, 2009 at 4:43 PM, Aniello Del Sorbo ani...@gmail.com wrote:

 2009/10/22 Niels Breet ni...@maemo.org:
  On Thu, October 22, 2009 15:31, gary liquid wrote:
  There is no interface to pull apps manually.
  if testing identifies a blocker, the maintainer has no way but to leave
 it
   there wasting the other testers time.
 
  This reminds me. If a maintainer votes his own app down, it should be
  removed instantly.
 
  This way a maintainer can easily remove his own app and not waste
 testers'
  time.
 

 /me likes that.

 --
 anidel
 ___
 maemo-developers mailing list
 maemo-developers@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-developers


/me too!

Luca Donaggio
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Screenshot as loading screen on Maemo 5

2009/10/22 Luca Donaggio donag...@gmail.com:
 On Sat, Oct 17, 2009 at 1:03 PM, Cornelius Hald h...@icandy.de wrote:

 On Sat, 2009-10-17 at 11:58 +0100, Aniello Del Sorbo wrote:
 
  My program doesn't ask anything when you close it, but it keeps
  automatically saving the document in
  a temporary file. Thus at every start it loads it up and you're back
  where you left.
  So I thought I would call the screenshot function at the very end,
  while closing down the program.
 
  It didn't work. It didn't save the screenshot of what was there.
 
  So I call it when I receive the expose event (like in the example) and
  it does work there.
  Why is that?
 
  I still have to investigate it, but I thought the window would be
  still available in my Quit function
  when called from the destroy event.

 I'm also calling it when quitting the application. I'm using the
 'delete-event' on my main window. There I call it just before
 gtk_main_quit(). It's working for me...

 Cheers!
 Conny


 ___
 maemo-developers mailing list
 maemo-developers@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-developers

 I'm resuming an old thread, sorry!

 If I call hildon_gtk_window_take_screenshot() within the callback function
 for the delete-event of the main app, just before gtk_main_quit(), it seems
 that something has already happened to the main window: it complains that it
 is not a GtkWindow (which usually is, as HildonWindow derives from it), but
 a GdkWindow, and, of course, no screenshot were taken.

 Luca Donaggio


I am doing the same and works, but then I was thinking that's it's
probably best doing at the
beginning, with a clean UI.

I thought that doing it at the end, before closing it, would then fake
a reload of the app in the state
it was left when closing it.

But this has an issue, which I think deserves thoughts:

1) to really speed up things you should take the screenshot only once.
2) if you do it at the end, before closing, for the reason above, then
you've got to take the screenshot
at every exit. This slows down the exit itself. And this is as much of
an issue as the startup speed.

Thus I thought I'll take the screenshot at the expose event and only
take it if the file is not there already.

-- 
anidel
Sent from London, Eng, United Kingdom
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Screenshot as loading screen on Maemo 5

2009-10-22 Thread Claudio Saavedra

El jue, 22-10-2009 a las 16:57 +0200, Luca Donaggio escribió:
 
 I'm resuming an old thread, sorry!
 
 If I call hildon_gtk_window_take_screenshot() within the callback
 function for the delete-event of the main app, just before
 gtk_main_quit(), it seems that something has already happened to the
 main window: it complains that it is not a GtkWindow (which usually
 is, as HildonWindow derives from it), but a GdkWindow, and, of course,
 no screenshot were taken.

Are you sure you are passing the right window to the function?
event-window is not the one (just in case).

Claudio


___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Screenshot as loading screen on Maemo 5

On Thu, Oct 22, 2009 at 5:06 PM, Aniello Del Sorbo ani...@gmail.com wrote:

 2009/10/22 Luca Donaggio donag...@gmail.com:
  On Sat, Oct 17, 2009 at 1:03 PM, Cornelius Hald h...@icandy.de wrote:
 
  On Sat, 2009-10-17 at 11:58 +0100, Aniello Del Sorbo wrote:
  
   My program doesn't ask anything when you close it, but it keeps
   automatically saving the document in
   a temporary file. Thus at every start it loads it up and you're back
   where you left.
   So I thought I would call the screenshot function at the very end,
   while closing down the program.
  
   It didn't work. It didn't save the screenshot of what was there.
  
   So I call it when I receive the expose event (like in the example) and
   it does work there.
   Why is that?
  
   I still have to investigate it, but I thought the window would be
   still available in my Quit function
   when called from the destroy event.
 
  I'm also calling it when quitting the application. I'm using the
  'delete-event' on my main window. There I call it just before
  gtk_main_quit(). It's working for me...
 
  Cheers!
  Conny
 
 
  ___
  maemo-developers mailing list
  maemo-developers@maemo.org
  https://lists.maemo.org/mailman/listinfo/maemo-developers
 
  I'm resuming an old thread, sorry!
 
  If I call hildon_gtk_window_take_screenshot() within the callback
 function
  for the delete-event of the main app, just before gtk_main_quit(), it
 seems
  that something has already happened to the main window: it complains that
 it
  is not a GtkWindow (which usually is, as HildonWindow derives from it),
 but
  a GdkWindow, and, of course, no screenshot were taken.
 
  Luca Donaggio
 

 I am doing the same and works, but then I was thinking that's it's
 probably best doing at the
 beginning, with a clean UI.

 I thought that doing it at the end, before closing it, would then fake
 a reload of the app in the state
 it was left when closing it.

 But this has an issue, which I think deserves thoughts:

 1) to really speed up things you should take the screenshot only once.
 2) if you do it at the end, before closing, for the reason above, then
 you've got to take the screenshot
 at every exit. This slows down the exit itself. And this is as much of
 an issue as the startup speed.

 Thus I thought I'll take the screenshot at the expose event and only
 take it if the file is not there already.

 --
 anidel
 Sent from London, Eng, United Kingdom


You're right, I moved the screenshot-taking process at the beginning too.
Where are the screenshots stored? Ie: which file I should check to determine
if a screenshot has already been taken once?
As a side fact: we should remove the existing screenshot when installing a
new version of our apps, as their appearance could have changed and the
stored screenshot could not reflect the current UI any more.

Luca Donaggio
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Screenshot as loading screen on Maemo 5

On Thu, Oct 22, 2009 at 5:11 PM, Claudio Saavedra csaave...@igalia.comwrote:

 El jue, 22-10-2009 a las 16:57 +0200, Luca Donaggio escribió:
 
  I'm resuming an old thread, sorry!
 
  If I call hildon_gtk_window_take_screenshot() within the callback
  function for the delete-event of the main app, just before
  gtk_main_quit(), it seems that something has already happened to the
  main window: it complains that it is not a GtkWindow (which usually
  is, as HildonWindow derives from it), but a GdkWindow, and, of course,
  no screenshot were taken.

 Are you sure you are passing the right window to the function?
 event-window is not the one (just in case).

 Claudio


 ___
 maemo-developers mailing list
 maemo-developers@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-developers


Thanks for the tip Claudio, but no, I'm using a reference to the main app
window (a HildonWindow), and I'm using g_signal_connect() which should call
my callback function before the default signal handlers.

Luca Donaggio
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Screenshot as loading screen on Maemo 5

They are stored in /home/user/.cache/launch/service name.pvr

Speaking of which, I shall change my service name.

Aniello

2009/10/22 Luca Donaggio donag...@gmail.com:
 On Thu, Oct 22, 2009 at 5:11 PM, Claudio Saavedra csaave...@igalia.com
 wrote:

 El jue, 22-10-2009 a las 16:57 +0200, Luca Donaggio escribió:
 
  I'm resuming an old thread, sorry!
 
  If I call hildon_gtk_window_take_screenshot() within the callback
  function for the delete-event of the main app, just before
  gtk_main_quit(), it seems that something has already happened to the
  main window: it complains that it is not a GtkWindow (which usually
  is, as HildonWindow derives from it), but a GdkWindow, and, of course,
  no screenshot were taken.

 Are you sure you are passing the right window to the function?
 event-window is not the one (just in case).

 Claudio


 ___
 maemo-developers mailing list
 maemo-developers@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-developers

 Thanks for the tip Claudio, but no, I'm using a reference to the main app
 window (a HildonWindow), and I'm using g_signal_connect() which should call
 my callback function before the default signal handlers.

 Luca Donaggio

 ___
 maemo-developers mailing list
 maemo-developers@maemo.org
 https://lists.maemo.org/mailman/listinfo/maemo-developers





-- 
anidel
Sent from London, Eng, United Kingdom
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Screenshot as loading screen on Maemo 5

2009-10-22 Thread Andrew Flegg

On Thu, Oct 22, 2009 at 16:06, Aniello Del Sorbo ani...@gmail.com wrote:

[snip]
 Thus I thought I'll take the screenshot at the expose event and only
 take it if the file is not there already.

I *think* you need to do it at every expose event. What if the user
changes theme and the font colours change (for example)?

Cheers,

Andrew

-- 
Andrew Flegg -- mailto:and...@bleb.org  |  http://www.bleb.org/
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Screenshot as loading screen on Maemo 5

2009/10/22 Andrew Flegg and...@bleb.org:
 On Thu, Oct 22, 2009 at 16:06, Aniello Del Sorbo ani...@gmail.com wrote:

 [snip]
 Thus I thought I'll take the screenshot at the expose event and only
 take it if the file is not there already.

 I *think* you need to do it at every expose event. What if the user
 changes theme and the font colours change (for example)?

 Cheers,

 Andrew

 --
 Andrew Flegg -- mailto:and...@bleb.org  |  http://www.bleb.org/


True.
But taking a snapshot slows down the startup... it should be then done
in a small thread?

-- 
anidel
Sent from London, Eng, United Kingdom
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Maemo-Optify Builder Bots = Broken?

2009-10-22 Thread Julius Luukko

Ed Bartosh wrote:
 2009/10/22 Kamen Bundev bun...@gmail.com:
 Hmm, yes, that seems to be the problem. In the final SDK /opt is a symlink
 but in the latest beta SDK it is not. I didn't upgrade my development
 machine, but I have the final on another so I can compare. I'll report back
 if successful.

 You're right.
 Autobuilder uses latest SDK and /opt is in the rootstrap:
 tar -ztf /scratchbox/packages/maemo-sdk-rootstrap_5.0_armel.tgz | grep 
 '^\./opt'
 ./opt
 
 I removed it from there and now packages with /opt directory should be
 installable.
 Try to re-upload your packages to autobuilder. It should work now.
 
 Thank you for your help.
 
 PS: Is someone willing to file a bug for SDK :) ?
 

Thanks Ed,

But did you forgot to do it for x86 target? armel builds now fine, but 
i386 does not [1]:

Unpacking libgtkextra-x11-2.0-1 (from 
.../libgtkextra-x11-2.0-1_2.1.1-3.1maemo4_i386.deb) ...
dpkg: error processing 
/var/cache/apt/archives/libgtkextra-x11-2.0-1_2.1.1-3.1maemo4_i386.deb 
(--unpack):
  trying to overwrite `/opt', which is also in package base-files
dpkg-deb: subprocess paste killed by signal (Broken pipe)

[1] https://garage.maemo.org/builder/fremantle/fuelpad_0.82-fremantle2/

-- 
Julius
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

AutoBuilders ignoring a depenancy

2009-10-22 Thread Nathan Anderson

Ed,

I resubmitted my package; and it decided to ignore one of my
dependency.  (But it did pull in the optified packages! g)

https://garage.maemo.org/builder/fremantle/sword_1.6.0a-0maemo1/armel.root.l
og.OK.txt Shows:

2009-10-22 17:46:55] Try to install static depends: 
libcurl3 libcurl3-dev libicu42 libicu42-dev clucene-core clucene-core-dev
zlib1g-dev python2.5 python2.5-dev maemo-optify

However the dsc file has:
https://garage.maemo.org/builder/fremantle/sword_1.6.0a-0maemo1/sources/swor
d_1.6.0a-0maemo1.dsc

Build-Depends: debhelper (= 5), libcurl3, libcurl3-dev, libicu42,
libicu42-dev, clucene-core, clucene-core-dev, zlib1g-dev, zlib1g, python2.5,
python2.5-dev, swig1.3, maemo-optify

It ignored my swig1.3 request.   The default swig inside
scratchbox/sdk is 1.3.29 -- It generates totally broken code for this
package so I took the debian packaged 1.3.40 and added the minor changes to
it to make it work on maemo.   It is listed in the extras repository as
swig1.3

Nathan.

___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: QA queue determine required thumbs down for removal

2009/10/22 Niels Breet ni...@maemo.org:
 On Thu, October 22, 2009 15:31, gary liquid wrote:
 There is no interface to pull apps manually.
 if testing identifies a blocker, the maintainer has no way but to leave it
  there wasting the other testers time.

 This reminds me. If a maintainer votes his own app down, it should be
 removed instantly.

We should also think about dependencies when packages are removed from
-testing.
If maintainer doesn't like his library and removes it what will happen
with another
application, which depends on this library? Theoretically it should be
also removed from -testing or rebuilt with older version of library if
it exists.
This situation can be resolved if autobuilder would build dependencies
only from extras.
However it can slow down the whole process, because developers would
have to wait
untill all needed libraries go to extras before they'll be able to
build their packages.

-- 
BR,
Ed
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: AutoBuilders ignoring a depenancy

2009/10/22 Nathan Anderson nat...@andersonsplace.net:
 Ed,

I resubmitted my package; and it decided to ignore one of my
 dependency.  (But it did pull in the optified packages! g)

 https://garage.maemo.org/builder/fremantle/sword_1.6.0a-0maemo1/armel.root.l
 og.OK.txt Shows:

 2009-10-22 17:46:55] Try to install static depends:
 libcurl3 libcurl3-dev libicu42 libicu42-dev clucene-core clucene-core-dev
 zlib1g-dev python2.5 python2.5-dev maemo-optify

 However the dsc file has:
 https://garage.maemo.org/builder/fremantle/sword_1.6.0a-0maemo1/sources/swor
 d_1.6.0a-0maemo1.dsc

 Build-Depends: debhelper (= 5), libcurl3, libcurl3-dev, libicu42,
 libicu42-dev, clucene-core, clucene-core-dev, zlib1g-dev, zlib1g, python2.5,
 python2.5-dev, swig1.3, maemo-optify

It ignored my swig1.3 request.   The default swig inside
 scratchbox/sdk is 1.3.29 -- It generates totally broken code for this
 package so I took the debian packaged 1.3.40 and added the minor changes to
 it to make it work on maemo.   It is listed in the extras repository as
 swig1.3

Just put swig1.3 (= 1.3.40) into Build-depends: line of your package.
It should solve the problem.

-- 
BR,
Ed
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Maemo-Optify Builder Bots = Broken?

2009/10/22 Julius Luukko julle.luu...@quicknet.inet.fi:

 But did you forgot to do it for x86 target? armel builds now fine, but i386
 does not [1]:

Oops, sorry. My bad.

Done. Should work now.

Just in case someone wants to do the same for their rootstraps. This
is what I did:

gunzip /scratchbox/packages/maemo-sdk-rootstrap_5.0_i386.tgz 
/tmp/maemo-sdk-rootstrap_5.0_i386.tar
tar --delete -f /tmp/maemo-sdk-rootstrap_5.0_i386.tar ./opt
mv /scratchbox/packages/maemo-sdk-rootstrap_5.0_i386.tgz
/scratchbox/packages/maemo-sdk-rootstrap_5.0_i386.tgz.withopt
gzip /tmp/maemo-sdk-rootstrap_5.0_i386.tar 
/scratchbox/packages/maemo-sdk-rootstrap_5.0_i386.tar.gz

-- 
BR,
Ed
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers

Re: Using the sharing plugins