Re: Dependency problems during packaging
On 2010-08-02 19:33, Kamilla Bremeraunet kami...@bremeraunet.com wrote: Hi, I'm trying to package FaceBrick, which is using libqfacebook in MADDE (instead of scratchbox, which I have heard works) and have run into some problems: At first when doing mad dpkg-buildpackage -us -uc it was complaining about not being able to find the file libqfacebookconnect.so.1 - I solved this by copying the file over to /home/kamilla/.madde/0.6.72/sysroots/fremantle-arm-sysroot-10.2010.19-1-slim/usr/lib/, but now I'm running into a different error: dh_makeshlibs dh_installdeb dh_shlibdeps dpkg-shlibdeps: failure: no dependency information found for /home/kamilla/.madde/0.6.72/sysroots/fremantle-arm-sysroot-10.2010.19-1-slim/usr/lib/libqfacebookconnect.so.1 (used by debian/facebrick/opt/facebrick/facebrick). dh_shlibdeps: command returned error code 512 make: *** [binary-arch] Error 1 dpkg-buildpackage: failure: debian/rules binary gave error exit status 2 Does anyone know what I need to do to fix this? If using third-party libraries with MADDE, you may wish to read the following talk thread: http://talk.maemo.org/showthread.php?t=48536 especially the last post, which mentions how to resolve your dh_shlibdeps problem, by copying /var/lib/dpkg/info/package.* of an installed package to the corresponding location in the MADDE sysroot. There was some discussion in June about these problems: http://lists.maemo.org/pipermail/maemo-developers/2010-June/026807.html -- David King | http://amigadave.com/ | dav...@openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Controlling N900 Display Brightness Display turn on
Hi, I need to control the Display Brightness Display Turn off(While it went to standby). For Display Turn on, I have increased the standby timer to 2 mins(max). But I need to increase it further more say 10 mins. Can I control that? For Display Brightness, I need to dim and bright the Display programatically, like using dbus commands. -Raja ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Controlling N900 Display Brightness Display turn on
praveen koduru wrote: Hi, I need to control the Display Brightness Display Turn off(While it went to standby). For Display Turn on, I have increased the standby timer to 2 mins(max). But I need to increase it further more say 10 mins. Can I control that? As I understand it, the general way to do this is to tell the system every 30s to keep the display on. This stops software accidentally leaving the display on. For Display Brightness, I need to dim and bright the Display programatically, like using dbus commands. I'm unsure if this is possible, I haven't investigated it. I'd look at the source of simple-brightness-widget. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Web Runtime in extras-devel
Just to let people know, our Nokian friends uploaded a new iteration of the Web Runtime preview to extras-devel. There is a slight change in the nomenclature, though, as we (maemo.org) requested an -experimental tag added to the package name, to avoid later clashes with potential official packages (like we had in the case of Qt packages). Special thanks to Xizhi for following this through. I suggest those that already installed the WRT, or depend on it, to replace their packages with the new ones. To avoid confusion, the old packages are in the process of being deleted from the repositories. Thanks for your attention and to everyone who made this possible. Best regards, Attila ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Begininer-PLZ HELP.
Hi, I am a 3rd year undergraduate student, computer science and engineering in India. My ambition is to do a Gsoc project in Maemo .Could you please give me information on how to go about the whole thing.Should I start with freemantle or diablo?Its pretty confusing.Please help me to develop myself for Gsoc. -- Cheers! Aswin Akhilesh B.Tech Computer Science and Engineering Amrita School of Engineering(Amritapuri) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Begininer-PLZ HELP.
Hello, On Tue, Aug 3, 2010 at 10:43 PM, akhilesh ashwin akhilesh...@gmail.comwrote: Hi, I am a 3rd year undergraduate student, computer science and engineering in India. My ambition is to do a Gsoc project in Maemo .Could you please give me information on how to go about the whole thing.Should I start with freemantle or diablo?Its pretty confusing.Please help me to develop myself for Gsoc. GSoC '10 is almost over, so only next year if we get accepted, in that case you should look at meego[1]. [1] - http://meego.com/ Best regards, -- Valério Valério http://www.valeriovalerio.org -- Cheers! Aswin Akhilesh B.Tech Computer Science and Engineering Amrita School of Engineering(Amritapuri) ___ 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: Begininer-PLZ HELP.
On Tue, Aug 3, 2010 at 10:43 PM, akhilesh ashwin akhilesh...@gmail.com wrote: My ambition is to do a Gsoc project in Maemo .Could you please give me information on how to go about the whole thing.Should I start with freemantle or diablo?Its pretty confusing.Please help me to develop myself for Gsoc. In a nutshell - learn Qt. -- Ville M. Vainio @@ Forum Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: [MeeGo-community] Open Letter/Proposal to allow Maemo on the MeeGo Community OBS
This issue has recently received some attention from this post onwards: http://bugs.meego.com/show_bug.cgi?id=615#c26 so I felt it worth re-posting this to remind people of the original request. Summary : We would like to support the Maemo community in migrating to MeeGo by allowing them to build open-source applications that link against a mix of open _and closed_ libraries on the MeeGo _Community_ OBS. Cross-posted again... please discuss on meego-community. Thanks. David PS as an aside we have almost finished the OSU deployment thanks to a long weekend. Details here: http://wiki.meego.com/Build_Infrastructure/Community_Builder/Installation On 15/06/10 18:16, David Greaves wrote: This is an open letter to the whole MeeGo community and on behalf of the Maemo development community. The purpose of this letter is to ask the MeeGo community for their permission to bring Maemo build targets (currently Fremantle eventually Harmattan, Diablo, Chinook?) to the MeeGo Community OBS and to ask the Maemo development community for their support in this project. *Please discuss on meego-community mailing list* I would like to emphasise that this is a Maemo Community initiative and is not being pushed by Nokia. At this point we are not aware of any similar initiatives related to the Moblin community but we would fully support any that arise. The Maemo community has built up around Nokia devices which, in many ways, are amongst the most open devices available in their class. There is a passion for openness in the Maemo community and we know that the future for this family of devices lies with MeeGo. Many of us are looking forward to MeeGo and are keen to transition as smoothly as possible. However our devices are not fully open and developing for them has dependencies on vendor proprietary binaries which would need to be available on the build service. This would mean putting closed binaries on the MeeGo OBS and having a part of the MeeGo Community OBS functionality being 'restricted' to Maemo developers. Naturally we recognise and respect that MeeGo is an open source project and there may be ideological issues in allowing closed binaries into the ecosystem (even though they're just for build/linking). We also recognise the risk of opening the door to closed binaries and suggest that this arrangement could be agreed as a one-time grandfathering in (http://en.wikipedia.org/wiki/Grandfather_clause) situation for the Maemo community. However we also feel that the benefits of supporting a smooth transition for the vibrant Maemo development community would be worthwhile both for MeeGo and Maemo: * developers would be able to use the OBS' natural ability to target Fremantle, Harmattan and MeeGo from a single location. This would bring more developers and their applications to MeeGo sooner. * many of the same people in the Maemo and MeeGo community teams look after the Maemo Autobuilder and the MeeGo application OBS. Our limited volunteer time would be used more effectively on a single platform instance. * resources earmarked for Maemo could be added to the MeeGo estate and would naturally be used at peak efficiency as Maemo demand decreases and MeeGo demand rises. * new Maemo community Quality Assurance processes would evolve around the shared OBS and could assist the development of MeeGo QA processes. and perhaps most important of all: * users of existing devices could expect a significantly longer maintainable life from products built on a consolidated build service and could look forward to their applications being available on MeeGo as soon as devices become available. The maemo.org buildservice already has a 'proof of concept' instance of the OBS which allows the Fremantle target to co-exist with a MeeGo target and we already intend to use this as a basis for the MeeGo community OBS. The proposed solution *must* allow MeeGo community users to use the MeeGo Community OBS without any reference to Nokia closed binaries; this facet of the service should be entirely optional. Equally the legal issues around the closed binaries require an EULA related to demonstrated possession of a relevant device. This can be handled in a similar manner to the Maemo Autobuilder service; ie registration of a serial# to a developer account. The proposal therefore is: * To provide the closed binaries as a build-target repository (probably DoD for those who know and care) on the community OBS. * To grant ACL based access to this repository based on acceptance of an EULA * To *not* require any such EULA for 'MeeGo-only' accounts on the service I've run this by Tero Kejo in Nokia and he's very supportive of the idea. From: David Greaves / lbt Community Member and build systems guy. Niels Breet / X-Fade maemo.org webmaster and autobuild owner Carsten Munk / Stskeeps maemo.org distmaster Andrew Flegg / Jaffa on behalf of the Maemo Community Council ___
Re: How to to manually package Qt Mobility?
On Wednesday 21 July 2010 17:10:11 Attila Csipa wrote: (in fact, it would be cool to see what *exactly* the Qt Ovi QA requirements are, not just generic descriptions - if someone has a link, I'd be grateful). FWIW, I got a link: http://blogs.forum.nokia.com/blog/ovi-publisher-alert/2010/08/02/qt-content-qa and the relevant section: Q: Can Qt Mobility APIs be used to create applications for Ovi Store? A: Qt Mobility can be used with applications for Symbian devices. For N900, Qt Mobilty is not officially supported yet so we cannot accept applications that use Qt Mobility. Regards, Attila ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Ask for package removal
The following packaged applications in repository are outdated and aren't up to date. Some are wrong licenced, some bugged lead users to do do crappy things. Please remove : - vectormine - pygtkeditor - py2deb - pypackager from the fremantle and fremantle-1.2 repository in extras-devel, extras-testing, extras Thanks -- Benoît HERVIER, Khertan Software - http://khertan.net/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers