Re: Maemo5 on Beagle
Carsten Valdemar Munk wrote: Hi all, I have uploaded my kernel at http://gitorious.org/maemo5-sgx-beagle/maemo5-beagle-cvm . It is omap-pm kernel with beagleboard patch on top, as well as few patches to get Nokia SGX module going. Defconfig is at http://rcn-ee.homeip.net:81/dl/omap/beagle/v2.6.29-e63cf07-pm42.1/defconfig (answer 'm' to the PVR module when doing make oldconfig) A compiled kernel can be found at http://www.daimi.au.dk/~cvm/repo/beaglepmsgx2.tar.gz. You will need to follow instructions on http://www.omappedia.org/wiki/Maemo_Getting_Started. When that is done, copy in http://www.daimi.au.dk/~cvm/sgx into /etc/event.d on the filesystem. Current status we have is that it boots Xorg just fine, hildon-desktop starts, except it seems to insist on outputting on LCD interface and leave DVI and S-video blank. Anyone who can check if it actually shows something on that interface? This can be fixed by using at kernel command line (e.g. via U-Boot's bootcmd) omapfb.mode=dvi:800x600mr...@60. Short status: 1. Build rootfs according to http://www.omappedia.org/wiki/Maemo_Getting_Started 2. Make sure you extract the resulting rootfs (image-rootfs.tgz) to SD card with tar --numeric-owner -pzxf image-rootfs.tgz 3. The rootfs doesn't contain any dev entries (makedev is missing). Workaround: Download and install in rootfs http://www.daimi.au.dk/~cvm/repo/makedev_2.3.2~2.3.1-80osso9_all.deb Then, in rootfs go to /dev directory and there manually do ../sbin/MAKEDEV std ../sbin/MAKEDEV consoleonly ../sbin/MAKEDEV maemo 4. Download http://www.daimi.au.dk/~cvm/repo/beaglepmsgx2.tar.gz It contains the kernel (uImage) and the kernel modules. Extract beaglepmsgx2.tar.gz in root of rootfs to have the kernel modules in place. Move uImage to boot partition of SD card (where u-boot.bin is located, too). 5. Download http://www.daimi.au.dk/~cvm/repo/zoom2.patch and install it in root of rootfs patch -p0 zoom2.patch 6. Download http://www.daimi.au.dk/~cvm/sgx and move it to etc/event.d/sgx 8. sync umount your SD card, boot into U-Boot 9. At U-Boot set kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait omapfb.mode=dvi:800x600mr...@60 10. Re-boot, enjoy booting it with Beagle :) After some time, having a DVI monitor connected, first the Beagle logo should be shown and then the water background. It disappears after ~1min and the monitor switches off. This seems to be the screen saver. Plugging/unplugging an USB mouse sometimes brings the screen back. Moving the mouse doesn't seem to help, though (Note: I already had no USB mouse working with Maemo alpha on Beagle). Further work: - I was not able to log in at minicom console. I got login prompt, but typing resulted in some garbage characters. Typing root/rootme there seemed to make the system hang and after some time the login prompt came again. - Disable screen blanking - Make (USB) mouse to show and work As I'm no expert on this, any help would be greatly appreciated! Many thanks to Carsten and Till for helping with this!! Cheers Dirk Debug tip: Observe your console log saying SGX 5, it means SGX succeeded in initializing. Pitfall: omap_pm_set_min_mpu_freq(sgx_dev, vdd1); is commented out in drivers/gpu/pvr/services4/system/omap3430/sysutils_linux.c. If anyone knows of any patches that contain the MPU stuff, it would be much welcome. Regards, Carsten Valdemar Munk Citat af tero.k...@nokia.com: - Original message - Dirk Behme wrote: Based on http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-omap_2.6.28.bb?h=stable/2009 I built a kernel with http://people.freedesktop.org/~felipec/beagle/0001-DSS2-Export-omap_dispc_set_plane_ba0.patch (needs manual editing, doesn't apply cleanly to above 2.6.28 Beagle kernel, see attachment) If anybody likes to test it with Maemo5 (SGX), I can send the uImage I took also the OE kernel and applied your patch on top of that. The rootfs tries to load pvrsvrkm, omaplfb, and pvr2d kernel modules. Where should I get these? Maybe Carsten can help? He has a kernel that goes pretty far. Tero -- Tuomas ___ maemo-developers mailing list maemo-developers@maemo.orgmailto: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: Maemo5 on Beagle
Dirk Behme wrote: Short status: [clip] 10. Re-boot, enjoy booting it with Beagle :) I followed these instructions roughly and got it running. Further work: - I was not able to log in at minicom console. I got login prompt, but typing resulted in some garbage characters. Typing root/rootme there seemed to make the system hang and after some time the login prompt came again. The serial console seems to work during the boot phase but it gets garbage later. It does work for me most of the time after finishing the boot up as well. Could this be related to power management..? - Disable screen blanking Unblanks when touching the USB mouse. - Make (USB) mouse to show and work WORKSFORME. I'm using a D-Link DUB-E100 USB ethernet dongle and at least I managed to install openssh using that. I haven't tried anything else yet (I need to get the curson showing first). -- Tuomas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Hildon Extras project launched
On Tue, 2009-10-27 at 14:30 -0400, Andrew Olmsted wrote: After taking WAY too long to do anything on this project, I have imported my initial color and font selectors to the Hildon Extras project. I edited the Makefile.am to include the source and header files, and added the following: - he-color-selector - he-color-dialog - he-color-button - he-font-selector - he-font-dialog - he-font-button Andrew, that's really great! Thanks a lot! I haven't done a build yet, mostly because I was having autotool difficulty. I haven't attempted to figure out whether it is my setup, or the scripts, but autogen.sh fails for me. I will send more information as I get it. Your code just compiles fine only my initial autogen.sh is not good - I'll fix now. My next goals are to make he-color-button and he-font-button use multiple labels, like he-check-button and other hildon buttons. I also want to implement a simple color selector, where the user can select from pre-loaded color samples. The option to use the RGB selector will still be available. I'm looking forward to the simple color selector. Hopefully I'll commit my transparent fullscreen thing (aka HeTransparentFullscreenThing ;)) this week too. BTW, is someone interested in writing a replacement for GtkAboutDialog? Cheers! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo5 on Beagle
The serial console seems to work during the boot phase but it gets garbage later. It does work for me most of the time after finishing the boot up as well. Could this be related to power management..? This happens on N900 too. OMAP-PM kernel issue (mentioned in OMAP-PM wiki). /Carsten ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo5 on Beagle
- Original message - Dirk Behme wrote: Short status: [clip] 10. Re-boot, enjoy booting it with Beagle :) I followed these instructions roughly and got it running. Ok, I need to make a fresh image from scratch. I guess my stuff is messed from trying different versions during the last week. (or then my monitor is messed) Further work: - I was not able to log in at minicom console. I got login prompt, but typing resulted in some garbage characters. Typing root/rootme there seemed to make the system hang and after some time the login prompt came again. The serial console seems to work during the boot phase but it gets garbage later. It does work for me most of the time after finishing the boot up as well. Could this be related to power management..? Yes. Power management puts serial console to sleep, but it does wake up when pressing keys. You'll also notice that after console inactivity the first character will be garbage, again power management at work. - Disable screen blanking Unblanks when touching the USB mouse. - Make (USB) mouse to show and work WORKSFORME. I'm using a D-Link DUB-E100 USB ethernet dongle and at least I managed to install openssh using that. I haven't tried anything else yet (I need to get the curson showing first). This could be a usb hub thing. I have gone through two or three usb hubs to get one that works as it should. The Xorg.0.log should tell that you have a mouse and keyboard. Tero -- Tuomas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Hildon Extras project launched
On Tue, 2009-10-27 at 14:30 -0400, Andrew Olmsted wrote: I haven't done a build yet, mostly because I was having autotool difficulty. I haven't attempted to figure out whether it is my setup, or the scripts, but autogen.sh fails for me. I will send more information as I get it. Should be fixed now. Please give it a try. Cheers! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo5 on Beagle
- Make (USB) mouse to show and work WORKSFORME. I'm using a D-Link DUB-E100 USB ethernet dongle and at least I managed to install openssh using that. I haven't tried anything else yet (I need to get the curson showing first). Oh, while I remember. You won't be seeing a cursor in this image. They removed the trick for transparent x cursor and hardcoded it in libmatchbox2. I have a patch for it in Mer that makes it show depending if a environment variable is set. Will dig it up later. If you can't wait, you will need to find it in libmatchbox2 (it is kinda easy to find) and remove that part, recompile libmatchbox2 and hildon-desktop which has libmatchbox2 statically linked. /Carsten ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: orca screen reader
From: jonathan j.nad...@charter.net Hello list, I was wondering if you knew about the orca screen reader working with the n900? Sorry if this isn't the right list to post to about this. Well you asked about a specific application on a maemo based device, so I bet that this is the correct list ;) AFAIK, nobody has tried to port orca screen reader to n900, or at least he didn't make public his efforts. Anyway, as other GNOME projects, probably it would be possible to make the migration, and shouldn't be really really complex (although probably some issues would appear). After all, other a11y related technologies were ported to Maemo, like GAIL, and a library to implement the a11y support for the hildon widgets were created, HAIL (HAIL is an add-on to GAIL, in the same way that the hildon widgets is an add-on to Gtk+). In the same way, there is an old project of maemo test automation using dogtail. Here the link: http://hildon-test-aut.garage.maemo.org/ === API (apinhe...@igalia.com) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Re: Maemo5 on Beagle
Hi, I'm using a D-Link DUB-E100 USB ethernet dongle and at least I managed to install openssh using that. I haven't tried anything else yet (I need to get the curson showing first). I just tried to include openssh into the image at build time. Adding the extras-devel repo is no problem, but qemu doesn't seem to be able to actually generate the keys. That's sad, it'd be nice to be able to provide a pretty complete rootfs without the need to install basic tools afterwards. I have just installed wpa_supplicant from extras-devel and since the kernel already included the rt73 driver, i was able to attach to a wpa protected wlan. Nice :-) This could be a usb hub thing. I have gone through two or three usb hubs to get one that works as it should. The Xorg.0.log should tell that you have a mouse and keyboard. Uhm, the SDK doesn't write a Xorg.0.log, does it? Till ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Re: Maemo5 on Beagle
-Original Message- From: ext Till Harbaum [mailto:li...@harbaum.org] --snip-- This could be a usb hub thing. I have gone through two or three usb hubs to get one that works as it should. The Xorg.0.log should tell that you have a mouse and keyboard. Uhm, the SDK doesn't write a Xorg.0.log, does it? My image does, to /tmp/Xorg.0.log don't know if that is the norm, but I thank Carsten for the rootfs :-) Tero Till ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo5 on Beagle
On Wed, 2009-10-28 at 09:59 +0100, ext Carsten Valdemar Munk wrote: ... If you can't wait, you will need to find it in libmatchbox2 (it is kinda easy to find) and remove that part, recompile libmatchbox2 and hildon-desktop which has libmatchbox2 statically linked. You can change (redefine) the cursor from any other program as well, does not have to be hildon-desktop... -Kimmo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: RE: Re: Maemo5 on Beagle
Hi, never mind, i didn't expect this to be in /tmp Till - original Nachricht Betreff: RE: Re: Maemo5 on Beagle Gesendet: Mi, 28. Okt 2009 Von: tero.k...@nokia.com -Original Message- From: ext Till Harbaum [mailto:li...@harbaum.org] --snip-- This could be a usb hub thing. I have gone through two or three usb hubs to get one that works as it should. The Xorg.0.log should tell that you have a mouse and keyboard. Uhm, the SDK doesn't write a Xorg.0.log, does it? My image does, to /tmp/Xorg.0.log don't know if that is the norm, but I thank Carsten for the rootfs :-) Tero Till --- original Nachricht Ende ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
More Git/Garage issues...
Hi, I was using Git with Garage just fine...until yesterday. Now, every time I try to push files to the project, I get this output: --- tims-macbook:hermes tim$ git push origin master error: Cannot access URL https://git.maemo.org/projects/hermes/, return code 22 error: failed to push some refs to 'https://git.maemo.org/projects/hermes' --- Anyone know why this might be happening? Andrew Flegg tested this on his end and was able to push. I didn't do anything to my config since it was working. Thanks! Tim -- http://samoff.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: More Git/Garage issues...
Hello, Tim Samoff wrote: Hi, I was using Git with Garage just fine...until yesterday. Now, every time I try to push files to the project, I get this output: --- tims-macbook:hermes tim$ git push origin master error: Cannot access URL https://git.maemo.org/projects/hermes/, return code 22 error: failed to push some refs to 'https://git.maemo.org/projects/hermes' --- Anyone know why this might be happening? Yes, anonymous pushes are no longer possible. They were allowed due to a misconfiguration, but we have fixed that. The 'SCM page' [1] of each projects tells what do you need for committing to the central repo. In a nutshell: Please make sure you have filled in your garage credentials to ~/.netrc. The info that needs to be added there is the following: machine git.maemo.org login __garage user name__ password __garage password__ Andrew Flegg tested this on his end and was able to push. I didn't do anything to my config since it was working. Andrew probably has a proper ~/.netrc on his workstation. Sorry for the inconveniences it may have caused. Thanks! Tim Cheers, ferenc -- maemo.org sysadmin, developer email: fer...@maemo.org [1] Hermes SCM page https://garage.maemo.org/scm/?group_id=1071 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo5 on Beagle
Carsten Valdemar Munk wrote: If you can't wait, you will need to find it in libmatchbox2 (it is kinda easy to find) and remove that part, recompile libmatchbox2 and hildon-desktop which has libmatchbox2 statically linked. I commented this part out of the MB: /* set the cursor invisible */ I recompiled and installed MB in SB, recompiled hildon-desktop and installed the new hildon-desktop in the device. But I still didn't see the cursor. Then I recompiled X without the --enable-null-root-cursor but still no luck. -- Tuomas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: More Git/Garage issues...
Hi, Please make sure you have filled in your garage credentials to ~/.netrc. The info that needs to be added there is the following: machine git.maemo.org login __garage user name__ password __garage password__ Thanks, Ferenc! All is well now. :) Tim -- http://samoff.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
My first day as maemo.org distmaster
Starting from today, I will be officially starting my work as maemo.org distmaster. Nokia has gracefully sponsored this position for the community at the request of the maemo.org community council. The current maemo.org team cover areas such as bug management, system administrationcollaboration spaces, documentation, forums and maintaining software repositories. All these positions facilitate development and collaboration in the community - one based around the Maemo platform and the Nokia devices. But one particular area is missing: the facilitation of tablet/device operating system development. While maemo.org currently targets developers building on top of the OS, many people within the community is interested in improving the OS, since it is what they have to deal with daily - as Maemo users. In my time within maemo.org I've found there's been a reliance on Nokia to provide fixes for problems - instead of looking within the community for people who were capable enough to fix the problem, deliver the solution and publish it in a manner that non-developers can utilize the fix. One of the maemo.org 2010 Agenda goals is to provide Maemo variants - which would be the pipeline for delivering community fixes. Maintaining a Maemo variant is not a easy job - you have to deal with a lot of different stakeholders in a diplomatic manner, mentor and engage new developers, often do a lot of the heavy lifting yourself, faciliate the developing and invent new collaboration spaces for this. Facilitating and engaging the community in this manner is a day job - which is why we have the maemo.org team. I will have 20 hours per week (part-time until January of my own choice) where I will be doing mostly community work and some internal Nokia work as needed. The primary role as a distmaster is defined as facilitating the development of Maemo variants (Mer, Diablo/Fremantle Community Variants, etc): * Developing collaboration spaces for developers of Maemo variants * Mentoring and engaging developers in order to move the Maemo platform and variants ahead * Communicating with stakeholders (Nokia, distributions implementing the Maemo platform, users and developers) Secondary role is serving as a paid system developer for the maemo.org community: * Developing fixes and features for the Maemo OS variants either on his/her own based on the input of maemo.org community council * or through activating, mentoring for and collaborating with community developer(s) in order to get it completed in collaboration with upstream developers. As I am also maintaining the ports and base system area for Mer, I will focus myself on the hardware support for Nokia devices and let other team members deal with other device communities/vendors to avoid any potential conflict of interest situations. As primary facilitator for the Mer project I've successfully helped activate many developers within the community in order to get Mer to where it is today. A lot of these developers came to the Maemo project at the hope of being able to develop the OS but ended up contributing few pieces to move ahead - but there was noone to group all these things and incorporate them in the system, so the brilliant pieces ended up gathering dust - until now. Now there's a official community position to make this work happen. Looking forward to working even more closely with this community. Regards, Carsten Valdemar Munk / Stskeeps ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: My first day as maemo.org distmaster
On Wed, Oct 28, 2009 at 14:03, Carsten Valdemar Munk c...@cs.au.dk wrote: Starting from today, I will be officially starting my work as maemo.org distmaster. Nokia has gracefully sponsored this position for the community at the request of the maemo.org community council. Congratulations! And can I be the first to say thank you to Nokia for seriously considering our proposal. It's a testament to the level of trust and respect that the community (and the Community Council) have in the eyes of Nokia's decision makers... ...of course, it helped having such a strong candidate as Carsten available! 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: Extras QA checklist
On Oct 27, 2009, at 12:53, Attila Csipa wrote: A few random thoughts, not pushing for anything. On Tuesday 27 October 2009 10:20:39 Andrew Flegg wrote: * MUST have bug tracker URL in XSBC-Bugtracker control field. This is a machine controllable thing, so if it's a MUST, it has nothing to with QA - it should be part of the autobuilder/promoter mechanism. * MUST NOT violate licences or copyright; MUST respect trademarks. This one is quite tricky. Currently, packages on Maemo often do not include license files, the package page also does not list a license so it's actually an effort to find out how a package/project is licensed and whether it's in compliance with it. Actually, this is not that hard. The license information has to be in the debian/copyright file. If the package comes from debian, you can be pretty sure that the license (i.e. the copyright file) is correct. In the debian perl group we go to significant lengths to get permissions from the copyright holder when the copyright is not obvious and we don't package something if we cannot determine the source of copyright. In maemo we have to be strict about this because no one wants a copyright violation so packagers are going to be asked to be diligent and follow this as a MUST. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Maemo 5 - Playing sounds from Qt
Hi, I'm looking for an easy way to play sounds for a small game I'm developing for Fremantle. I'm using the Fremantle Qt port. I tried using libcanberra, and my example works on the desktop, but when I move it to Scratchbox, I get a CA_ERROR_NOTAVAILABLE when I call ca_context_play(). As a side note, *I think* using libcanberra requires me to put my ogg sounds in /usr/share/sounds ... which seems a bit like hacking. I feel like I'm abusing the canberra API to do something it's not supposed to do. Should I be doing something different? Is there a better API? What do linux game developers usually use for playing short sounds? Can anybody provide any examples? -Topi ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: My first day as maemo.org distmaster
Hi, On Wed, Oct 28, 2009 at 2:11 PM, Andrew Flegg and...@bleb.org wrote: On Wed, Oct 28, 2009 at 14:03, Carsten Valdemar Munk c...@cs.au.dk wrote: Starting from today, I will be officially starting my work as maemo.org distmaster. Nokia has gracefully sponsored this position for the community at the request of the maemo.org community council. Congratulations! And can I be the first to say thank you to Nokia for seriously considering our proposal. It's a testament to the level of trust and respect that the community (and the Community Council) have in the eyes of Nokia's decision makers... ...of course, it helped having such a strong candidate as Carsten available! very glad to see this new position, congrats to the ones that made it happen. My best wishes for our new member of the gang-of-four, err... now should be gang-of-five :) Best regards, -- Valério Valério Maemo Community Council Chair http://www.valeriovalerio.org 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 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo 5 - Playing sounds from Qt
Hello! I tried using libcanberra, and my example works on the desktop, but when I move it to Scratchbox, I get a CA_ERROR_NOTAVAILABLE when I call ca_context_play(). [...] Should I be doing something different? Is there a better API? What do linux game developers usually use for playing short sounds? Can anybody provide any examples? AFAIK, libcanberra is mainly for triggering playing system sounds (from some system sound theme), like in play the sound the OS defiens to be played when I pressing a button. For playing any sound (and much more :-)) you can use the gstreamer API. take a look at: http://maemo.org/development/sdks/maemo_5_api_documentation/ Section Multimedia APIs -- Gruß... Tim ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo 5 - Playing sounds from Qt
Thanks for the reply, Tim. Isn't it a bit of an overkill to set up an entire GST pipeline just to play a blip sound? Is there something more lightweight? -Topi On Wed, Oct 28, 2009 at 4:51 PM, Tim Teulings r...@edge.ping.de wrote: Hello! I tried using libcanberra, and my example works on the desktop, but when I move it to Scratchbox, I get a CA_ERROR_NOTAVAILABLE when I call ca_context_play(). [...] Should I be doing something different? Is there a better API? What do linux game developers usually use for playing short sounds? Can anybody provide any examples? AFAIK, libcanberra is mainly for triggering playing system sounds (from some system sound theme), like in play the sound the OS defiens to be played when I pressing a button. For playing any sound (and much more :-)) you can use the gstreamer API. take a look at: http://maemo.org/development/sdks/maemo_5_api_documentation/ Section Multimedia APIs -- Gruß... Tim ___ 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: My first day as maemo.org distmaster
On Oct 28, 2009, at 10:50 AM, Valerio Valerio wrote: On Wed, Oct 28, 2009 at 2:11 PM, Andrew Flegg and...@bleb.org wrote: On Wed, Oct 28, 2009 at 14:03, Carsten Valdemar Munk c...@cs.au.dk wrote: Starting from today, I will be officially starting my work as maemo.org distmaster. Nokia has gracefully sponsored this position for the community at the request of the maemo.org community council. Congratulations! And can I be the first to say thank you to Nokia for seriously considering our proposal. It's a testament to the level of trust and respect that the community (and the Community Council) have in the eyes of Nokia's decision makers... ...of course, it helped having such a strong candidate as Carsten available! very glad to see this new position, congrats to the ones that made it happen. My best wishes for our new member of the gang-of-four, err... now should be gang-of-five :) Arguably gang-of-six if you're counting Reggie, though his role is more administrative than anybody else's. ;) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo 5 - Playing sounds from Qt
Hello! Isn't it a bit of an overkill to set up an entire GST pipeline just to play a blip sound? Yes, but if you want to play your own sound or any sound on the filesystem this seems the way to go (libcanberra is for predefined sounds for predefined events). Lower level ways are likely forbitten, higher level ways likely require more code. Is there something more lightweight? You can use playbin (or playbin2?) for simplifing the pipeline building process. That still makes it a number of lines of code (but of course you will wrap that into a helper method :-)). -- Gruß... Tim ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo 5 - Playing sounds from Qt
Hi, You can use phonon to play video and sound with Qt for fremantle. It's available in current 4.5 community port as well as in the official 4.6 port. It's cross-platform, anyhow you can read more about that at: http://doc.trolltech.com/4.5/phonon-overview.html Br, Antonio On Wed, Oct 28, 2009 at 5:12 PM, Tim Teulings r...@edge.ping.de wrote: Hello! Isn't it a bit of an overkill to set up an entire GST pipeline just to play a blip sound? Yes, but if you want to play your own sound or any sound on the filesystem this seems the way to go (libcanberra is for predefined sounds for predefined events). Lower level ways are likely forbitten, higher level ways likely require more code. Is there something more lightweight? You can use playbin (or playbin2?) for simplifing the pipeline building process. That still makes it a number of lines of code (but of course you will wrap that into a helper method :-)). -- Gruß... Tim ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- Pablo Picassohttp://www.brainyquote.com/quotes/authors/p/pablo_picasso.html - Computers are useless. They can only give you answers. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: My first day as maemo.org distmaster
Carsten Valdemar Munk ha scritto: Starting from today, I will be officially starting my work as maemo.org distmaster. Nokia has gracefully sponsored this position for the community at the request of the maemo.org community council. Wow, I am glad to see this level of involvment from Nokia. Congratulations for the post and good luck ;-) A. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Extras QA checklist
On Wednesday 28 October 2009 15:23:14 Jeremiah Foster wrote: Actually, this is not that hard. The license information has to be in the debian/copyright file. If the package comes from debian, you can be pretty sure that the license (i.e. the copyright file) is correct. I was mostly referring to packages that are not straight Debian ports but rather 'native' (or significantly altered) Maemo applications. But we do not need to go that far. Often even really basic building blocks lack proper license/attribution information (for example Qt itself has no debian/copyright or license files included. Probably not commercial edition, but is it GPL or LGPL ? Maybe both ?). Anyway, I'm among the first ones to check for licensing info, and the current approach (leaving it out from the binary packages because of space considerations and not displaying it anywhere on the maemo.org web interface) does not make it any easier. Surely burling through the debian dir of source packages is not the best/easiest long-term way of doing this, especially if it's something *QA testers* are supposed to do ? Regards, Attila ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Optification breaks package on upgrade from non-optified older version
Marius Vollmer marius.voll...@nokia.com writes: I have pushed a new version of maemo-optify to gitorious that patches maintainer scripts to do late optification for stuff that dpkg didn't do. It's not very well tested yet, of course, so please dig in! http://maemo.gitorious.org/maemo-af/maemo-optify I have now released maemo-optify 0.1 to the fremantle buildbot with this change. It should now be possible to update a non-optified version of a package to a optified version. Everybody, please test! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Extras QA checklist
On Wednesday 28 October 2009 16:45:56 Attila Csipa wrote: proper license/attribution information (for example Qt itself has no debian/copyright or license files included. Probably not commercial To make this a bit more precise before someone misunderstands - the binary package is missing the license files, the source package has three different license files in there (GPL, LGPL, and commercial preview), and figuring out which one(s) apply requires going through debian/rules and analyzing/running the ./configure script). Regards, Attila ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo5 on Beagle
Hi, Am Dienstag 27 Oktober 2009 schrieb Carsten Valdemar Munk: I have uploaded my kernel at http://gitorious.org/maemo5-sgx-beagle/maemo5-beagle-cvm . It is omap-pm kernel with beagleboard patch on top, as well as few patches to get Nokia SGX module going. Defconfig is at http://rcn-ee.homeip.net:81/dl/omap/beagle/v2.6.29-e63cf07-pm42.1/defconfig (answer 'm' to the PVR module when doing make oldconfig) Doesn't work for me: $ git clone git://gitorious.org/maemo5-sgx-beagle Initialized empty Git repository in /scratchbox/users/harbaum/home/harbaum/beagleboard/maemo5-sgx-beagle/.git/ fatal: protocol error: expected sha/ref, got ' -- Cannot find repository: /maemo5-sgx-beagle --' What's that? Till ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
maemo-optify, autobuilder /opt
Hi, I've put together a suggested spec for the decision, taken at the summit during the /opt BOF[1], that the auto-builder would run some maemo-optify version during the build process (controlled by a control file header): http://talk.maemo.org/showthread.php?p=359996#post359996 I suggest the header is XS-Maemo-Optify, and has the following values: none: no optification should be done, or considered, by the autobuilder. manual: the application author will do optification manually. If the package contains no entries under /opt it would be considered a build failure. auto: maemo-optify would be run if certain heuristics were met (e.g. no entries in /opt, no Python dependency) force: maemo-optify would always be run Marius: are you taking ownership of talking to Ed Bartosh, and anyone else, about this plan? Thanks in advance, Andrew [1] http://lists.maemo.org/pipermail/maemo-developers/2009-October/021289.html -- 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: Maemo5 on Beagle
Hi, nevermind, i am just too stupid to copy'n paste ... It should be git clone git://gitorious.org/maemo5-sgx-beagle/maemo5-beagle-cvm.git Till Am Mittwoch 28 Oktober 2009 schrieb Till Harbaum / Lists: Hi, Am Dienstag 27 Oktober 2009 schrieb Carsten Valdemar Munk: I have uploaded my kernel at http://gitorious.org/maemo5-sgx-beagle/maemo5-beagle-cvm . It is omap-pm kernel with beagleboard patch on top, as well as few patches to get Nokia SGX module going. Defconfig is at http://rcn-ee.homeip.net:81/dl/omap/beagle/v2.6.29-e63cf07-pm42.1/defconfig (answer 'm' to the PVR module when doing make oldconfig) Doesn't work for me: $ git clone git://gitorious.org/maemo5-sgx-beagle Initialized empty Git repository in /scratchbox/users/harbaum/home/harbaum/beagleboard/maemo5-sgx-beagle/.git/ fatal: protocol error: expected sha/ref, got ' -- Cannot find repository: /maemo5-sgx-beagle --' What's that? Till ___ 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: Maemo 5 - Playing sounds from Qt
Is even Phonon really used for snappy/lightweight audio playback?
It *appears* that PulseAudio is usable according to here:
http://maemo.org/development/sdks/maemo_5_api_documentation/
With the code below on host, I can get a wav file to play. That same wav
file won't play when I move everything to scratchbox... I get the
following...
[sbox-FREMANTLE_X86: ~/test2] fakeroot run-standalone.sh ./test2 cat1.wav
main.cpp: pa_simple_new() failed: Connection refused
Does anyone know what could be wrong?
I compiled with qmake -project and added the pulseaudio-simple library with
LIBS+=
CODE START--
/***
This file is part of PulseAudio.
PulseAudio is free software; you can redistribute it and/or modify
it under the terms of the GNU Lesser General Public License as published
by the Free Software Foundation; either version 2.1 of the License,
or (at your option) any later version.
PulseAudio is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU Lesser General Public License
along with PulseAudio; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
USA.
***/
#ifdef HAVE_CONFIG_H
#include config.h
#endif
#include stdio.h
#include unistd.h
#include string.h
#include errno.h
#include fcntl.h
#include pulse/simple.h
#include pulse/error.h
#include pulse/gccmacro.h
#define BUFSIZE 1024
int main(int argc, char*argv[]) {
/* The Sample format to use */
/*static const pa_sample_spec ss = {
.format = PA_SAMPLE_S16LE,
.rate = 44100,
.channels = 2
};*/
static const pa_sample_spec ss = {PA_SAMPLE_U8, 22050, 1};
pa_simple *s = NULL;
int ret = 1;
int error;
/* replace STDIN with the specified file if needed */
if (argc 1) {
int fd;
if ((fd = open(argv[1], O_RDONLY)) 0) {
fprintf(stderr, __FILE__: open() failed: %s\n,
strerror(errno));
goto finish;
}
if (dup2(fd, STDIN_FILENO) 0) {
fprintf(stderr, __FILE__: dup2() failed: %s\n,
strerror(errno));
goto finish;
}
close(fd);
}
/* Create a new playback stream */
if (!(s = pa_simple_new(NULL, argv[0], PA_STREAM_PLAYBACK, NULL,
playback, ss, NULL, NULL, error))) {
fprintf(stderr, __FILE__: pa_simple_new() failed: %s\n,
pa_strerror(error));
goto finish;
}
for (;;) {
uint8_t buf[BUFSIZE];
ssize_t r;
#if 0
pa_usec_t latency;
if ((latency = pa_simple_get_latency(s, error)) == (pa_usec_t) -1)
{
fprintf(stderr, __FILE__: pa_simple_get_latency() failed:
%s\n, pa_strerror(error));
goto finish;
}
fprintf(stderr, %0.0f usec\r, (float)latency);
#endif
/* Read some data ... */
if ((r = read(STDIN_FILENO, buf, sizeof(buf))) = 0) {
if (r == 0) /* EOF */
break;
fprintf(stderr, __FILE__: read() failed: %s\n,
strerror(errno));
goto finish;
}
/* ... and play it */
if (pa_simple_write(s, buf, (size_t) r, error) 0) {
fprintf(stderr, __FILE__: pa_simple_write() failed: %s\n,
pa_strerror(error));
goto finish;
}
}
/* Make sure that every single sample was played */
if (pa_simple_drain(s, error) 0) {
fprintf(stderr, __FILE__: pa_simple_drain() failed: %s\n,
pa_strerror(error));
goto finish;
}
ret = 0;
finish:
if (s)
pa_simple_free(s);
return ret;
}
--CODE END---
On Wed, Oct 28, 2009 at 5:31 PM, Antonio Aloisio
antonio.aloi...@gmail.comwrote:
Hi,
You can use phonon to play video and sound with Qt for fremantle.
It's available in current 4.5 community port as well as in the official 4.6
port.
It's cross-platform, anyhow you can read more about that at:
http://doc.trolltech.com/4.5/phonon-overview.html
Br,
Antonio
On Wed, Oct 28, 2009 at 5:12 PM, Tim Teulings r...@edge.ping.de wrote:
Hello!
Isn't it a bit of an overkill to set up an entire GST pipeline just to
play
a blip sound?
Yes, but if you want to play your own sound or any sound on the filesystem
this seems the
way to go (libcanberra is for predefined sounds for predefined events).
Lower level ways are likely forbitten, higher level ways likely require
more code.
Is there something more lightweight?
You can use playbin (or playbin2?) for simplifing the pipeline building
process. That still
makes it a number of lines of code (but of course you will wrap that into
a
helper method :-)).
--
Gruß...
Tim
___
maemo-developers mailing list
Re: Maemo 5 - Playing sounds from Qt
On Wed, 2009-10-28 at 19:36 +0200, Topi Hukkanen wrote: [sbox-FREMANTLE_X86: ~/test2] fakeroot run-standalone.sh ./test2 cat1.wav main.cpp: pa_simple_new() failed: Connection refused Does anyone know what could be wrong? It might be that the pulseaudio daemon is not running. I know it's not running in the Beta2 SDK. Try to start it manually, also please have a look at this bug: https://bugs.maemo.org/show_bug.cgi?id=5168 Cheers! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo 5 - Playing sounds from Qt
Thanks for the heads-up, Conny. But... could there be more things wrong? [sbox-FREMANTLE_X86: ~/test2] run-standalone.sh pulseaudio OIL: ERROR liboiltest.c 405: oil_test_check_impl(): function mas10_u8_mmx_2 in class mas10_u8_l15 failed check (7843 0) || (outside=0) pulseaudio: symbol lookup error: /usr/lib/libpulsecore-0.9.15.so: undefined symbol: eventfd [sbox-FREMANTLE_X86: ~/test2] This is after apt-get update / apt-get upgrade, of course. -Topi On Wed, Oct 28, 2009 at 7:43 PM, Cornelius Hald h...@icandy.de wrote: On Wed, 2009-10-28 at 19:36 +0200, Topi Hukkanen wrote: [sbox-FREMANTLE_X86: ~/test2] fakeroot run-standalone.sh ./test2 cat1.wav main.cpp: pa_simple_new() failed: Connection refused Does anyone know what could be wrong? It might be that the pulseaudio daemon is not running. I know it's not running in the Beta2 SDK. Try to start it manually, also please have a look at this bug: https://bugs.maemo.org/show_bug.cgi?id=5168 Cheers! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Extras QA checklist
* MUST NOT introduce security risks. I'd rephrase MUST NOT contain known security vulnerabilities and MUST specify a security vulnerability reporting contact point. This would take the ambiguity out of a security *risk* (almost nothing is risk-free). Vulnerabilities, however, are more tangible. There is, of course, still a class of vulnerabilities that could result in a debate, but much less so than when talking about risk. Known is also tricky - known by whom? - but it could suffice, as if anyone who is actually involved in this QA checking knows, it would trigger this. The contact point would usually be an email address and perhaps an associated GPG key, but the bug tracker could also suffice if the project is really keen on full disclosure. - Antti ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo 5 - Playing sounds from Qt
On Wed, 2009-10-28 at 19:49 +0200, Topi Hukkanen wrote: Thanks for the heads-up, Conny. But... could there be more things wrong? [sbox-FREMANTLE_X86: ~/test2] run-standalone.sh pulseaudio OIL: ERROR liboiltest.c 405: oil_test_check_impl(): function mas10_u8_mmx_2 in class mas10_u8_l15 failed check (7843 0) || (outside=0) pulseaudio: symbol lookup error: /usr/lib/libpulsecore-0.9.15.so: undefined symbol: eventfd [sbox-FREMANTLE_X86: ~/test2] I also get an error like that, but without the symbol lookup error part. After that is seems to be running (it's taking connections) but it does not output audio. Probably because there's already pulseaudio running on the host. Maybe it's possible to run puseaudio on the host and make it somehow available to scratchbox? Sorry that I cannot help you more. Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Extras QA checklist
On Oct 28, 2009, at 16:45, Attila Csipa wrote: On Wednesday 28 October 2009 15:23:14 Jeremiah Foster wrote: Actually, this is not that hard. The license information has to be in the debian/copyright file. If the package comes from debian, you can be pretty sure that the license (i.e. the copyright file) is correct. I was mostly referring to packages that are not straight Debian ports but rather 'native' (or significantly altered) Maemo applications. But we do not need to go that far. No - I think you are right, packages that are not straight ports need to be scrutinized. :) Often even really basic building blocks lack proper license/attribution information (for example Qt itself has no debian/copyright or license files included. Probably not commercial edition, but is it GPL or LGPL ? Maybe both ?). Anyway, I'm among the first ones to check for licensing info, and the current approach (leaving it out from the binary packages because of space considerations and not displaying it anywhere on the maemo.org web interface) does not make it any easier. Surely burling through the debian dir of source packages is not the best/easiest long-term way of doing this, especially if it's something *QA testers* are supposed to do ? Yeah, this is kind of detailed work and hard to automate, but I think we ought to try and do some type of automated check and raise a flag if we see copyright issues. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Extras QA checklist
On Oct 28, 2009, at 19:28, Antti Vähä-Sipilä wrote: * MUST NOT introduce security risks. I'd rephrase MUST NOT contain known security vulnerabilities and MUST specify a security vulnerability reporting contact point. This makes sense to me. This would take the ambiguity out of a security *risk* (almost nothing is risk-free). Vulnerabilities, however, are more tangible. There is, of course, still a class of vulnerabilities that could result in a debate, but much less so than when talking about risk. Known is also tricky - known by whom? - but it could suffice, as if anyone who is actually involved in this QA checking knows, it would trigger this. Perhaps a check against the CVE database? The contact point would usually be an email address and perhaps an associated GPG key, but the bug tracker could also suffice if the project is really keen on full disclosure. Seems reasonable. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-optify, autobuilder /opt
2009/10/28 Andrew Flegg and...@bleb.org: Hi, I've put together a suggested spec for the decision, taken at the summit during the /opt BOF[1], that the auto-builder would run some maemo-optify version during the build process (controlled by a control file header): http://talk.maemo.org/showthread.php?p=359996#post359996 I suggest the header is XS-Maemo-Optify, and has the following values: none: no optification should be done, or considered, by the autobuilder. manual: the application author will do optification manually. If the package contains no entries under /opt it would be considered a build failure. auto: maemo-optify would be run if certain heuristics were met (e.g. no entries in /opt, no Python dependency) force: maemo-optify would always be run Marius: are you taking ownership of talking to Ed Bartosh, and anyone else, about this plan? We can discuss it here. Sorry, I seem to miss the whole point of this activity. Why do you need to do that on autobuilder side? As far as I understood it's just a matter of including maemo-optify as a build dependency and run it in debian/rules, right? Why developer can't do this then? I don't see much difference between setting XS-Maemo-Optify and changes I mentioned above. In both cases developer should understand what optification means. BTW, when you want to have it done? I'm going to vacation in a couple of weeks. Before that I was going to finish implementation of multiple packages builds if I have time. -- BR, Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-optify, autobuilder /opt
Wouldn't it be better to leave the none option out considering the lack of storage space in N900. It can be made available in Harmattan. Regards: Bundyo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Extras QA checklist
Known is also tricky - known by whom? - but it could suffice, as if anyone who is actually involved in this QA checking knows, it would trigger this. Perhaps a check against the CVE database? That could be a plus, but many vulnerabilities never get CVE entries (for various reasons). So I'd still say known - if it's in the CVE database, it's definitely known but it would also cover those known only internally to the project. - Antti ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo5 on Beagle
tero.k...@nokia.com wrote: - Disable screen blanking Unblanks when touching the USB mouse. - Make (USB) mouse to show and work WORKSFORME. I'm using a D-Link DUB-E100 USB ethernet dongle and at least I managed to install openssh using that. I haven't tried anything else yet (I need to get the curson showing first). This could be a usb hub thing. I have gone through two or three usb hubs to get one that works as it should. The Xorg.0.log should tell that you have a mouse and keyboard. How do you guys connect USB to Beagle? Via USB 2.0 EHCI HS connector (#8 in [1])? Or use USB 2.0 HS OTG connector (#12 in [1]) with a special Mini-A plug? Most probably you then connect keyboard and mouse at powered hub? I normally use OTG connector with special Mini-A plug (was necessary for rev A and B Beagles) and powered hub. With this, mouse and keyboard worked at least fine with Angstrom. Thanks Dirk [1] http://elinux.org/BeagleBoard#Components ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo5 on Beagle
Hi, Am Mittwoch 28 Oktober 2009 schrieb Dirk Behme: How do you guys connect USB to Beagle? Via USB 2.0 EHCI HS connector (#8 in [1])? Or use USB 2.0 HS OTG connector (#12 in [1]) with a special Mini-A plug? Most probably you then connect keyboard and mouse at powered hub? Via OTG and a powered hub. Till ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo 5 - Playing sounds from Qt
Phonon uses GStreamer. Anyway if ou are using Qt, phonon is the best solution. Br, Antonio On Wed, Oct 28, 2009 at 8:34 PM, Cornelius Hald h...@icandy.de wrote: On Wed, 2009-10-28 at 19:49 +0200, Topi Hukkanen wrote: Thanks for the heads-up, Conny. But... could there be more things wrong? [sbox-FREMANTLE_X86: ~/test2] run-standalone.sh pulseaudio OIL: ERROR liboiltest.c 405: oil_test_check_impl(): function mas10_u8_mmx_2 in class mas10_u8_l15 failed check (7843 0) || (outside=0) pulseaudio: symbol lookup error: /usr/lib/libpulsecore-0.9.15.so: undefined symbol: eventfd [sbox-FREMANTLE_X86: ~/test2] I also get an error like that, but without the symbol lookup error part. After that is seems to be running (it's taking connections) but it does not output audio. Probably because there's already pulseaudio running on the host. Maybe it's possible to run puseaudio on the host and make it somehow available to scratchbox? Sorry that I cannot help you more. Conny -- Samuel Goldwynhttp://www.brainyquote.com/quotes/authors/s/samuel_goldwyn.html - I'm willing to admit that I may not always be right, but I am never wrong. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-optify, autobuilder /opt
Ed wrote: I've put together a suggested spec for the decision, taken at the summit during the /opt BOF[1], that the auto-builder would run some maemo-optify version during the build process (controlled by a control file header): Sorry, I seem to miss the whole point of this activity. Why do you need to do that on autobuilder side? As far as I understood it's just a matter of including maemo-optify as a build dependency and run it in debian/rules, right? Why developer can't do this then? I don't see much difference between setting XS-Maemo-Optify and changes I mentioned above. In both cases developer should understand what optification means. The consensus at the BOF was that since it's something which SHOULD be done for all Maemo packages, but that this is Maemo specific, that it should be done at the autobuilder to ensure that as many packages are optified as possible. By having auto be the default (i.e. the developer has NOT specified XS-Maemo-Optify) at some point in the future we can avoid the current problem where, even though the requirements are well understood more than half the user-facing applications in -testing aren't using /opt. BTW, when you want to have it done? I'm going to vacation in a couple of weeks. Before that I was going to finish implementation of multiple packages builds if I have time. i don't know, it's not my baby :-) One would imagine, in a perfect world, that if this was being done then: * We'd have a conclusion on the Python issue and a comment from the Qt folks. * XS-Maemo-Optify would be agreed and the builder and maemo-optify(-deb) changes made with 'none' as the default. * We could opt our packages in for the testing period, then change the default to auto, rebuild everything and not suffer any more rootfs problems. Given the small rootfs is the single largest problem which is going to impact reviews and opinion about the N900 we'd have it done ASAP. But then I no longer have to think of anybody else's priorities, that's somebody else's problem :) 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: maemo-optify, autobuilder /opt
Kamen wrote: Wouldn't it be better to leave the none option out considering the lack of storage space in N900. It can be made available in Harmattan. The thought was that there might be a small, or niche, product which just wouldn't work with maemo-optify and changing it to use /opt would be impractical. By not being too dictatorial the developer isn't pushed into their own repo. Similarly, if the bind mount is the best solution to the Python issue, Python modules might need to specify 'none' until auto's heuristic is updated to exclude them (Python modules would continue to install into /usr/lib/python2.5/site-packages under this solution, but the FS knows that that's some path under /opt really). 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
Maemo5 MicroB: javascript API for fullscreen, location, cursor enable?
Hello all I'm looking for any information about MicroB maemo-specific javascript API to do the following things: - Switch to fullscreen - Access location information - Enable the cursor Any hints? Thanks -Tom ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-optify, autobuilder /opt
I think it is good to be able to keep maemo-optify out of Build-Depends : This way we can keep the same debian control file for Diablo and Fremantle. I suppose the Diablo builder will only ignore the optify header ? Fred On Wed, Oct 28, 2009 at 8:10 PM, Ed Bartosh bart...@gmail.com wrote: 2009/10/28 Andrew Flegg and...@bleb.org: Hi, I've put together a suggested spec for the decision, taken at the summit during the /opt BOF[1], that the auto-builder would run some maemo-optify version during the build process (controlled by a control file header): http://talk.maemo.org/showthread.php?p=359996#post359996 I suggest the header is XS-Maemo-Optify, and has the following values: none: no optification should be done, or considered, by the autobuilder. manual: the application author will do optification manually. If the package contains no entries under /opt it would be considered a build failure. auto: maemo-optify would be run if certain heuristics were met (e.g. no entries in /opt, no Python dependency) force: maemo-optify would always be run Marius: are you taking ownership of talking to Ed Bartosh, and anyone else, about this plan? We can discuss it here. Sorry, I seem to miss the whole point of this activity. Why do you need to do that on autobuilder side? As far as I understood it's just a matter of including maemo-optify as a build dependency and run it in debian/rules, right? Why developer can't do this then? I don't see much difference between setting XS-Maemo-Optify and changes I mentioned above. In both cases developer should understand what optification means. BTW, when you want to have it done? I'm going to vacation in a couple of weeks. Before that I was going to finish implementation of multiple packages builds if I have time. -- BR, Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- Sent from La Rochelle, France ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-optify, autobuilder /opt
On Wednesday 28 October 2009 20:39:57 Andrew Flegg wrote: Ed wrote: BTW, when you want to have it done? I'm going to vacation in a couple of weeks. Before that I was going to finish implementation of multiple packages builds if I have time. i don't know, it's not my baby :-) One would imagine, in a perfect world, that if this was being done then: * We'd have a conclusion on the Python issue and a comment from the Qt folks. * XS-Maemo-Optify would be agreed and the builder and maemo-optify(-deb) changes made with 'none' as the default. * We could opt our packages in for the testing period, then change the default to auto, rebuild everything and not suffer any more rootfs problems. I think we should do the second item before Ed goes on holiday, even if it means deferring the multiple package builds. We can then test it (setting the header to auto in various packages) while Ed is away but there is minimal danger of problems cropping up while he is away. Ed, could we do that? Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Extras QA checklist
On Wednesday 28 October 2009 18:28:24 Antti Vähä-Sipilä wrote: * MUST NOT introduce security risks. I'd rephrase MUST NOT contain known security vulnerabilities and MUST specify a security vulnerability reporting contact point. The second requirement is not reasonable. Many small programs, particularly one-person projects, don't need a security vulnerability reporting contact point. There is already a maintainer field (mandatory) and the maintainer is the contact point. In fact, I am not even keen to allow an optional security vulnerability reporting contact point as that will mean creating yet another Maemo-specific package control field. And known means known by the developer -- no more and no less. Of course, once a tester has found a security bug and reported it, it is known by the developer so that means it cannot proceed until the bug is fixed. Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-optify, autobuilder /opt
2009/10/28 Andrew Flegg and...@bleb.org: Ed wrote: I've put together a suggested spec for the decision, taken at the summit during the /opt BOF[1], that the auto-builder would run some maemo-optify version during the build process (controlled by a control file header): Sorry, I seem to miss the whole point of this activity. Why do you need to do that on autobuilder side? As far as I understood it's just a matter of including maemo-optify as a build dependency and run it in debian/rules, right? Why developer can't do this then? I don't see much difference between setting XS-Maemo-Optify and changes I mentioned above. In both cases developer should understand what optification means. The consensus at the BOF was that since it's something which SHOULD be done for all Maemo packages, but that this is Maemo specific, that it should be done at the autobuilder to ensure that as many packages are optified as possible. By having auto be the default (i.e. the developer has NOT specified XS-Maemo-Optify) at some point in the future we can avoid the current problem where, even though the requirements are well understood more than half the user-facing applications in -testing aren't using /opt. Somehow I don't like the idea of doing anything with the package without developer being aware of this. I'd rather implement check on autobuilder side to insure that packages are optified. Developer can use option XS-Maemo-Optify: none to disable optification if developer doesn't want it. Explicit is better than implicit. (C) Zen of Python :) -- BR, Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-optify, autobuilder /opt
On Wednesday 28 October 2009 22:50:25 Ed Bartosh wrote: Somehow I don't like the idea of doing anything with the package without developer being aware of this. I'd rather implement check on autobuilder side to insure that packages are optified. Developer can use option XS-Maemo-Optify: none to disable optification if developer doesn't want it. Nobody likes doing something to the package automatically but, after a long discussion at the BOF, we agreed that the alternatives were even worse [1]. In particular, there was a strong argument that the package should not have to include anything (even a control field option) to cause optification to happen. Packages which wanted to do their own optification or which had to disable optification would have to include an option to stop optification. If it makes you happier: rename the autobuilder as autobuilder and optifier! We did agree that there had to be a way for developers to generate packages in the scratchbox environment which had been optified in exactly the same way the autobuilder would. And that we would update the wiki pages about checking packages will build to include using that tool to test the optification. So, the consensus decision was that the solution would be that autobuilder should automatically optify by default. Graham [1] It reminds me of the famous quote from Winston Churchill: Democracy is the worst form of government, except for all those other forms that have been tried from time to time. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
The issue of version strings
One thing I think it might be worth working on is the user- friendliness of the version strings of packages in Extras. We want the Application manager to be as friendly and approachable for the average user as possible and long incomprehensible lines of alphanumerics are a surefire way to scare people off. ;) So, this is just my humble request that people be considerate of users when crafting their version strings and try to it reasonable. Avoiding date/svn-based versions would probably be a good idea. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Extras-testing Marathon – Next Saturday (Oct 31)
Are you a lucky N900 owner ? Want to help the Maemo Community ? This call is for you. In the next Saturday(Oct 31) from 2pm till 7pm(UTC/GMT) we’ll host a testing marathon at #maemo-test...@freenode, in order to make more awesome community applications available for end users. This marathon will be also a test for our community QA process[1], we want to test it and improve it before the N900 hits the shelves. If you’re a developer, make sure your applications are in good shape before the testing marathon. More info: http://www.valeriovalerio.org/?p=289 Join the discussion here: http://talk.maemo.org/showthread.php?t=33164 [1] - http://wiki.maemo.org/Extras-testing Best regards, -- Valério Valério Maemo Community Council Chair http://www.valeriovalerio.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Extras-testing Marathon – Next Saturday (Oct 31)
On Oct 28, 2009, at 10:03 PM, Valerio Valerio wrote: If you’re a developer, make sure your applications are in good shape before the testing marathon. Any developers who would like Bugzilla products before the marathon starts, please email me the information listed on this page[1]: http://wiki.maemo.org/Bugs:Adding_Extra_products This is a nice way to reward your reporters with karma and can help you in tracking and treating bugs in your application. [1]https://bugs.maemo.org/enter_bug.cgi?classification=Extras ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: maemo-optify, autobuilder /opt
2009/10/29 Graham Cobb g+...@cobb.uk.net: I think we should do the second item before Ed goes on holiday, even if it means deferring the multiple package builds. We can then test it (setting the header to auto in various packages) while Ed is away but there is minimal danger of problems cropping up while he is away. Ed, could we do that? I think we can. I just want to understand why this way. -- BR, Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
