Re: Garage maintenance break
Hi, Thomas Waelti wrote: And now we have rush-hour on garage... dog slow, four apps queued inside 20 minutes. Is that new server slower or faster than the old one :-) Thanks for keeping an eye on that infrastructure, it really becomes critically important now. We did not move to the new server yet. The maintenance break was a pure mistake. Best regards -Tom Br, ferenc Hello, Marius Gedminas wrote: On Sat, Dec 12, 2009 at 11:34:57AM +, Andrew Flegg wrote: Apologies if such an announcement was made - but I didn't see it, and can't find it if it was. So, if it *was* made; it needs to be made more clearly next time :-) I was unable to find an announcement either. Since previous maintenance breaks used to be announced, I can only assume this downtime is unscheduled. Some kind of emergency? There was no announcement, because there was no maintenance break planned. What happened was a bad mistake from me. I changed the PosgreSQL config file to do some db migration stuff to the new server. After copying the database I forgot to revert the config changes which caused that the web site went down. I am very sorry for inconveniences it has caused. Br, ferenc ___ 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: Bootstrapping the Maemo 6 Developer Guide
Good idea! Moved page (with a redirect in place). Cheers, Dave. Keywan Najafi Tonekaboni wrote: Hi, Am Freitag, den 11.12.2009, 14:07 +0200 schrieb Quim Gil: Have you ever seen a Developer Guide being created from scratch? Now is your chance, also to get involved. Complain and be bold now so we all have a better time when the time to install the Maemo 6 SDK comes. :) http://wiki.maemo.org/Developer_Guide_table_of_contents This is good news. I would propose some Maemo 6 in the title, so nobody confuse this with the other (even though it's mention in the text). I have started the discussion at http://talk.maemo.org/showthread.php?t=36646 since I believe we are getting many newcomers (and less Linux experienced) developers there. You can give your feedback here if you prefer. Oh, fragmented maemo communication... we need a Mailinglist-to-Forum-to-Mailinglist-Converter (something like Gmane, but instead of for Newsgroups for Talk) Cheers, Keywan -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Find out Maemo version from script
Hi, I know this has been discussed before, but unfortunately I cannot find it. While developing inside the SDK I used /etc/maemo_version (which is provided by the package maemo-version) to alter the runtime behavior of some scripts. Now on the device I noticed that the package maemo-version does not exist. It seems to be in the SDK repositories only. How do you find out which version of Maemo your script is running on? Shouldn't the package maemo-version just be available in the default repositories? Thanks! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
pymaemo-optify: upgrading to the newer 0.3 version on Maemo 5
Hi all, This message is intended for those users already using the PyMaemo optification solution on Maemo 5. You are probably using it if you have extras-testing or extras-devel enabled on your N900. The extras repository does not contain pymaemo-optifier yet. A bug was identified (see https://bugs.maemo.org/show_bug.cgi?id=6886) which breaks Python packages when pymaemo-optify is upgraded on the command line using apt-get upgrade and some other Python package is upgraded at the same time. I uploaded a fixed package to extras-devel, but any upgrade from an older version, if done with some another Python package upgrade at the same time, will again trigger the bug. Therefore you need to upgrade only the pymaemo-optify package; later you can upload other Python packages without problem. From the command line == # apt-get install pymaemo-optify This will upgrade *only* pymaemo-optify. Using Application Manager Once the new version enters the repositories you have enabled, you should see a package upgrade notification for the pymaemo-optify package (version 0.3). If you don't see it, you don't have to do anything; it will appear at some point. Once you see the upgrade notification, upgrade *only* the pymaemo-optify package. Later you can upgrade any other packages. If you had already been affected by the bug = Run these commands on the terminal to cleanup your Python installation: # apt-get purge pymaemo-optify Then install *only* pymaemo-optify first (make sure you are installing 0.3 version): # apt-get update # apt-get install pymaemo-optify Now you can reinstall other Python applications you want. That's it. You have any problems with the upgrade, you can comment on the bug, or send an e-mail to the pymaemo-developers mailing list: https://garage.maemo.org/mailman/listinfo/pymaemo-developers/ Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: pymaemo-optify: upgrading to the newer 0.3 version on Maemo 5
On Tue, Dec 15, 2009 at 7:53 AM, Anderson Lizardo anderson.liza...@openbossa.org wrote: I uploaded a fixed package to extras-devel, but any upgrade from an older version, if done with some another Python package upgrade at the same time, will again trigger the bug. Therefore you need to upgrade only the pymaemo-optify package; later you can upload other Python packages without problem. Unfortunately, while this version fixed the upgrade issue, it broke clean installations... I sent a fixed version (0.4) that should fix this. So please, give as more testing to this new version (once it becomes available to extras-devel) as possible: clean installations, recovery from backup, upgrades through the installation manager. The same instructions from the rest of the e-mail applies, but use 0.4 instead. Thanks, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
QA process for middleware (libfoo, python-bar) packages: some ideas
Hi, I'm not sure if there's a better list to send this (or even if it is better to user talk.maemo.org), so feel free to redirect me to the write channel. In lack of a better name for the packages the packages that exist solely as enablers for developing our great GUI applications. So far, looks like the QA process is gearing towards the user/GUI applications. For instance, the thumbs up/down system is restricted to applications is user/* categories, and the QA testers are not instructed to check for possible problems in packages outside this category. I believe we can improve on this area: to have safer and optimized middleware packages, such as libraries, language bindings, data packages, build tools, and so on. While the user will obviously notice bugs with on the UI, problems with the middleware (for instance, some unknown symbol bug or a segfault due to unexpected ABI changes) are likely to be the most serious ones IMHO. Let me give some examples of such possible bugs: * A new version of libfoo is uploaded with unexpected ABI (Application Binary Interface) changes. At the same time some application is compiled against it and it works fine, so the package (together with libfoo) is promoted to extras. OTOH, this new version libfoo does not play well with the existing packages in extras, which will break or even fail to start * A new version of python-foo (some binding for libfoo) is uploaded to extras-devel, but contains a serious flaw that makes it segfault when calling method xyz(). At the same time, GUI application is uploaded which depends on that newer version, but does not use xyz() at all. In this case, the current QA checks would basically allow the application and python-foo to enter extras, but some future application which tries to use xyz() will segfault, blocking it from entering extras until python-foo is fixed. I have some ideas to improve (and assure) the quality of middleware packages: * Require (or strongly recommend) *all* packages to have at least some sort of unit/functional testing. In fact, most packages imported from Debian has tests, but what usually happens is that they are disabled so the package can build on scratchbox. * Have some way to run these tests automatically from the package sources when uploading packages to the autobuilder. * Exercise installation of packages (maybe using piuparts? See http://packages.debian.org/sid/piuparts), if possible on a real device. * Test disk-full conditions, and randon errors during package installation of packages from Extras. * Promote usage of ABI check tools. Any other ideas? Regards, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to get n900 IMEI code in C
On Mon, Nov 16, 2009 at 10:08, Dave Neary dne...@maemo.org wrote: Graham Cobb wrote: However, many of the CSD services can be discovered using various DBus tools. I have made a start on that and have put the information I have worked out so far in the Wiki of one of my garage projects. You can see this at: https://garage.maemo.org/plugins/wiki/index.php?CSD%20programming%20informationid=1106type=g Great! Any chance that you could put this is the main Maemo wiki, please? The issue with d-feet or similar is that there is no semantic information associated with the interfaces. Given there's also the top example at http://wiki.maemo.org/User:Jebba#DBUS, I think there's value in consolidating this information at a central: http://wiki.maemo.org/Phone_control Graham/Jebba: what do you think? 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: Find out Maemo version from script
There is /etc/osso_software_version but the file is part of some package that can be uninstalled. Then there is osso-product-info command that reads it from config partition (where it is stored by flasher) and prints it. Why do you need it? Maybe checking specific version of specific feature/debian package is better that this? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Find out Maemo version from script
On Tue, Dec 15, 2009 at 12:21:58PM +0100, Cornelius Hald wrote: While developing inside the SDK I used /etc/maemo_version (which is provided by the package maemo-version) to alter the runtime behavior of some scripts. I think it's simpler to check the version of some installed packages (using e.g. pkg-config) Berto ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Find out Maemo version from script
On Tue, Dec 15, 2009 at 04:37:23PM +0100, Alberto Garcia wrote: On Tue, Dec 15, 2009 at 12:21:58PM +0100, Cornelius Hald wrote: While developing inside the SDK I used /etc/maemo_version (which is provided by the package maemo-version) to alter the runtime behavior of some scripts. I think it's simpler to check the version of some installed packages (using e.g. pkg-config) And it's even better to check for the *features* you want, rather than the version of the software that has these features. Marius Gedminas -- At most companies, programmers aren't trusted with words that a user might actually see (and for good reason, much of the time). -- Joel Spolski signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Find out Maemo version from script
On Tue, 2009-12-15 at 17:44 +0200, Marius Gedminas wrote: On Tue, Dec 15, 2009 at 04:37:23PM +0100, Alberto Garcia wrote: On Tue, Dec 15, 2009 at 12:21:58PM +0100, Cornelius Hald wrote: While developing inside the SDK I used /etc/maemo_version (which is provided by the package maemo-version) to alter the runtime behavior of some scripts. I think it's simpler to check the version of some installed packages (using e.g. pkg-config) And it's even better to check for the *features* you want, rather than the version of the software that has these features. Thanks Frantisek, Alberto and Marius! I think I will use the osso-product-info command as this seems to be the best way for me to do it. With the other solutions I have some problems: * /etc/osso_software_version does not exist on my N900. * pkg-config is only for *-dev packages and does not exist (by default) on the N900. * Checking for the feature is not possible, as the feature is a bug in some preinstalled library and I don't know in which one. I need this check because I need to figure out whether or not this bug exists and if yes change a couple of files to work around it. So checking for the OSSO_PRODUCT_RELEASE_VERSION with the osso-product-info command should work for me. Thanks for all the suggestions! Conny ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On Dec 14, 2009, at 14:02, Anderson Lizardo wrote: On Mon, Dec 14, 2009 at 7:15 AM, Marius Vollmer marius.voll...@nokia.com wrote: On balance, I think it is better to just stick to debhelper 5 in Fremantle. And from our experience in PyMaemo backporting various (but not that many) packages from debhelper compatibility level 7 to 5, in most cases you need just to change: * debian/compat: 7 - 5 * debian/control: Build-Depends: debhelper (= 7) - debhelper (= 5) * And maybe comment out a few dh_* calls from debian/rules, which might not exist on level 5 One of the huge advantages of moving to debhelper 7 compat is that you can have your debian/rules files look like this: #!/usr/bin/make -f %: dh $@ Simple. You pass everything off to debhelper. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
OpenCV for Maemo5
Does anyone know where I can find OpenCV package for Maemo5 ? thanks, jesus ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Find out Maemo version from script
On Tue, Dec 15, 2009 at 07:50:48PM +0100, Cornelius Hald wrote: I think I will use the osso-product-info command as this seems to be the best way for me to do it. With the other solutions I have some problems: * /etc/osso_software_version does not exist on my N900. * pkg-config is only for *-dev packages and does not exist (by default) on the N900. * Checking for the feature is not possible, as the feature is a bug in some preinstalled library and I don't know in which one. I need this check because I need to figure out whether or not this bug exists and if yes change a couple of files to work around it. So checking for the OSSO_PRODUCT_RELEASE_VERSION with the osso-product-info command should work for me. This sounds very interesting. Can you tell use what the bug is and what files you need to change for the workaround? Marius Gedminas -- If the ancients were right and to think is to exist, does Microsoft exist? signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Debug info on device
Hi, I'm wondering is there a way to get debug information from a g_debug call when running your app on the device? Is it output to a specific log file or do I have to set something to get it working? I had assumed that running from xterm would show it but that isn't working Thom ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debug info on device
El mar, 15-12-2009 a las 23:14 +, Thomas Troy escribió: Hi, I'm wondering is there a way to get debug information from a g_debug call when running your app on the device? Is it output to a specific log file or do I have to set something to get it working? I had assumed that running from xterm would show it but that isn't working If I'm not mistaken, all that info will go into the syslog. But in production devices there's no sysklogd. You should install it from the development tools repository. http://wiki.maemo.org/Documentation/devtools/maemo5 Claudio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: OpenCV for Maemo5
On Tue, 2009-12-15 at 18:21 -0300, Jesus Sanchez-Palencia wrote: Does anyone know where I can find OpenCV package for Maemo5 ? I used this package https://garage.maemo.org/projects/opencv/ in FREMANTLE with the n900. This is an old version but it works! You can also download the version you're looking for and compile it yourself; I had to remove python support in order to succeed with the compilation. BTW CMake is now working if you pretend to compile version 2. Victor Fragoso. thanks, jesus ___ 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: OpenCV for Maemo5
Yes, thanks. Actually I had everything compiled and running when I sent the email, but I was just wondering why I didn't find any packages... Yes, I also had to remove python support in order to succeed. Thanks! jesus 2009/12/15 Victor Fragoso vfrag...@cs.ucsb.edu On Tue, 2009-12-15 at 18:21 -0300, Jesus Sanchez-Palencia wrote: Does anyone know where I can find OpenCV package for Maemo5 ? I used this package https://garage.maemo.org/projects/opencv/ in FREMANTLE with the n900. This is an old version but it works! You can also download the version you're looking for and compile it yourself; I had to remove python support in order to succeed with the compilation. BTW CMake is now working if you pretend to compile version 2. Victor Fragoso. thanks, jesus ___ 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
Commands for adjusting screen brightness for N810
Hi all, I know there's an built-in application for managing the display (brightness, etc), although I am curious if there are any commands (I am guessing it'll be D-BUS commands if there's any) to manipulate the screen brightness directly, or commands to manipulate all the display settings for that matter. If there's none, are there any ways run the built-in display program (at Control panel) via commands? Thanks, Jey Han ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Autobuilder and compiling against MCE
I'm attempting to compile an app with some MCE defines for portrait mode on the fremantle autobuilder. It seems that the mce-dev package is not installed on the autobuilder[1][2]. Is there an alternative to MCE that I am not aware of? All of the Fremantle examples for portrait mode show includes to mce. I'm a little confused. Thanks, Michael [1] https://garage.maemo.org/builder/fremantle/stopish_0.9.1-1/ [2] https://garage.maemo.org/builder/fremantle/stopish_0.9.1-2/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Debhelper 7
On Tuesday 15 December 2009 22:10:39 ext Jeremiah Foster, you wrote: * debian/compat: 7 - 5 * debian/control: Build-Depends: debhelper (= 7) - debhelper (= 5) * And maybe comment out a few dh_* calls from debian/rules, which might not exist on level 5 One of the huge advantages of moving to debhelper 7 compat is that you can have your debian/rules files look like this: #!/usr/bin/make -f %: dh $@ Simple. You pass everything off to debhelper. That takes care of the packaging part, but not the building part or does it? AFAICT, if you really want short and implicit rules, you could use CDBS. That works fine with any debhelper from version 4 and up. -- Rémi Denis-Courmont Nokia Devices RD, Maemo Software, Helsinki ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Does anyone see this?
Not only did I see your post, but I can confirm your problem, as I have the same: My own emails sent to the list never arrive in my mailing list inboxes, even though I have the settings in the subscriper page set as you describe. Anyone else with that problem? We might need to open a bug in bugzilla. Best regards -Tom Can someone please confirm that they can see this email? There have been some issues with post seeing my own postings (even though in the subscriber page the appropriate option is checked off as Yes) and also anyone seeing my emails on any of the two lists. Thanks ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
