Q: Maemo Extras Builder dependency failure
Hi, I keep getting a dependency error[1] from hildonmm package that for some reason requires hildon-1 package not to be found anywhere: --build fails--- checking for HILDON... configure: error: Package requirements (hildonmm hildon-fmmm) were not met: Package hildon-1 was not found in the pkg-config search path. Perhaps you should add the directory containing `hildon-1.pc' to the PKG_CONFIG_PATH environment variable Package 'hildon-1', required by 'hildonmm', not found Looking at Maemo Extras Assistant (Chinook extras rebuild) status page [2], I can see that hildonmm_0.9.7-2 builds fine, but hildon-1 package is not in the list. My scratchbox chinook ARMEL target has both hildonmm and hildon-1. What dependencies do I need to add to my package to make Extras Assistant pull and install hildon-1? So far, I have this in my debian/control file: -- Build-Depends: debhelper (= 4.0.0), libxml2-dev, libhildonmm-dev, libhildon-fmmm-dev, intltool, libassa-dev -- If hildonmm was successfully built and it depends on hildon-1, then making my package depend on hildonmm-dev should have taken care of dependency on hildon-1. thanks in advance, --vlg [1] https://garage.maemo.org/builder/chinook/granule_1.4.0-6/armel.build.log.FAILED.txt [2] https://garage.maemo.org/extras-assistant/maemo_extras_chinook_rebuild.php ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: can't find maemomm in 3.0 repo
Further digging reveals that starting with libsigc++-2.0-0c2a, the 'Section: libs' in debian/control file is considered a violation of some sort. osso-application-installer insists on having 'Section: user/FOO' as the least. I am afraid, all the packages have to be rebuilt, signed, and uploaded again. --Vlad-- On Mon, 2007-03-26 at 21:12 +, [EMAIL PROTECTED] wrote: Hi, on my n800 I am trying to install an application that depends on 'hildon-fmmm' package. It is, however, marked as 'Not installable' citing missing 'hildon-fmmm' (as well as all its immediate dependencies). My Application Manager catalog repository entry is: Catalog name: maemo-extras-3.0 Web address: http://repository.maemo.org/extras/ Distribution: 3.0 Components: free non-free Catalog refresh works ok, but I don't see hildon-fmmm_0.9.1-0 in a list of 'All' installable applications. Chasing down the path, I can clearly see the .deb itself available: http://repository.maemo.org/extras/pool/3.0/free/h/hildon-fmmm/ What am I doing wrong? thanks, --Vlad-- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] maeomm and gtkmm for Maemo 3.0 Bora
On Mon, 2007-01-22 at 12:51 +0100, Murray Cumming wrote: gtkmm and maemomm packages are now available in extras. More on my blog: http://www.murrayc.com/blog/permalink/2007/01/22/maemomm-maemo-for-c-with-gtkmm/ thanks! ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] signing up packages under FC5
Hi, my development platform is Fedora Core 5. In order for me to upload a package to maemo repo, I have to sign it [1] with $ debsign -kkey_id i386.changes $ debsign -kkey_id armel.changes according to step 5. of [1]. The wiki also warns not to do it from the scratchbox. But, I use FC5, and there is no 'debsign' in sight. Searching the web reveals that debsign belongs to the 'devscripts' package, to which there is no equivalent for FC5. So, what would be the equivalent procedure for signing .changes/.dsc file under Fedora Core? [1] https://maemo.org/maemowiki/ExtrasRepository [2] This message has been cross-posted to InternetTabletTalk/Software/Developers forum thanks for any tips, --Vlad ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Discussion of a possible project - offline calendar project
Mathias, can I suggest also to look at JPilot [1]? It already has a good presence on desktops, syncs with existing palms and might be a viable alternative. Written in C, it shurely will require some amount of facelift to fit nicely into 770's form-factor. It also comes with plugin framework and some plugins already available [2] (I personally like 'KeyRing' one). Plus, some sort of syncing with destop would be required as well. -Vlad [1] http://www.jpilot.org/ [2] http://www.jpilot.org/plugins.html On Sun, 2007-01-14 at 23:16 +0100, Mathias Uebelacker wrote: Hello, i would like to invitate you to discuss a project idea that i have. In the last past weeks a played around with an idea to create an offline caledar like the go ogle calendar. After my device chrashed yesterday this project becomes a higher priority. Till yesterday a worked on my timetracker project. Exactly on a modul which creates for every task an file which can be imported by the calendar. Well here some thoughts from my project sheet: - which language should be used ( C, Python...) - how should the data stored (database, file ...) - should the application interacts with osso applications (Adressbook, email) - limitation of the screen size (N770) - look and feel like the original ?? - exchange with the google calendar (import/export) - language files (for each user his or her language) - and and and I read all the mails about N770 / N800 and how to get one of the nuggets. So i would develop the tool for the N770 and this is the device, that most of us have. So far so good okay i think the project need more than one developer so i would like to invitate your to this project. In my opinion we have these sections to h andle: core dev ui database or file interface language file design (look and feel as the basis for the ui dev) Here we go please let me know what do you think about this project. Maybe there is a person which works on an project like this or nobody needs an offline calen dar If there some developer which will start these project with me let me know. If we can build a Team i will ask the garage-team to host that project so that we ca n start the work. br Mathias ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] maemo-apps.org application catalog
It seems that GTK community (as well as KDE) had faced at some point similar problems - their solution was GnomeFiles (KDE Apps) (http://gnomefiles.org/index.php, http://www.kde-apps.org/). -Vlad On Sat, 2006-09-30 at 05:24 -0700, Greg Morgan wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Siarhei Siamashka wrote: Hello All, What do you think about current wiki based application catalog? In my opinion, it is quite a large page already, slow to open and hard to navigate. A snip Thoughts? Maemo is a growing community. In some ways I see Maemo experiencing the same things that happened to the Fedora effort. Red Hat wanted to involve the community just like Nokia is doing. They did not create a forum and wiki right away so someone else did. Eventually a community evolves solving some of the problems. Maemo is spread out. The garage was a great idea of Nokia's to try an pull all those applications into one location as developers get used to the idea. Some developers like to have their own sites so you will never see them join the garage. The wiki application page was a good solution to collecting all these far flung resources and applications. Now that there are a larger number of applications the catalog needs to evolve too as you mention. Here are a number of ways to evolve the catalog. Some of these help me solve these problems for myself as a Nokia 770 user. 1.) When a wiki is young it is just good to throw content out there in order to seed pages for the community to work on. It encourages others to say on this is started I can add some of my knowledge to it. There's enough content now in the Maemo wiki that categories need to be applied to some of the pages. You can see a list here http://maemo.org/maemowiki/CategoryCategory . One of the benefits that the categories provides is a self maintaining list of pages. All you have to do is add one or more categories to a page and it is automatically in the list(s). For example, the Flasher page, http://maemo.org/maemowiki/Flasher_tool_usage , has two categories, CategoryFlashing CategoryHowToMisc. When someone clicks on the CategoryFlashing link of the Flasher_tool_usage page, then you can see all the related pages that have been classified the same way as shown here http://maemo.org/maemowiki/CategoryFlashing . You see it would be much easier to add a Misc link to the CategoryHowToMisc page, on the HowTo page http://maemo.org/maemowiki/CategoryHowToMisc , than to maintain the individual links as it is presently done on the HowTo page, http://maemo.org/maemowiki/HowTo . So far I just have the Misc section categorized and the other how to categories created. 2.) Even with the categorized pages, a list of applications needs to be maintained to locate all the available applications. There are some problems with this idea too. This page would just have wiki page names on it. Here's an example that I can show you on another wiki I hack on http://phpwebsite-comm.sourceforge.net/wiki/index.php?title=Third_Party_Themes . The Third Party Themes page has a list of a similar project with far flung resources. A new user can come to this page and shop for either free or cost themes for their content management system. 3.) The problem that Siarhei points out is that the catalog page is too slow to load. Item 2 above points to a solution for resolving this problem. The wiki detailed content that is now on the main application page can be cut and pasted into individual pages. At first just the initial content from the main page can be cut and pasted into a new page. For example, AppOssoXterm would be used for the ossoxterm application. The leading App would help prevent other page name conflicts, etc. in the Maemo wiki. Here are two example pages from the other wiki http://phpwebsite-comm.sourceforge.net/wiki/index.php?title=Default http://phpwebsite-comm.sourceforge.net/wiki/index.php?title=Colors . Note that both the pages follow a similar template. An application template can be developed for the Nokia application pages. In fact, the current Maemo catalog page has the rough outline of what each individual page should contain. Note two things that I am starting to do with the Colors page. I have created a category so that a person can shop by a theme author. Example, http://phpwebsite-comm.sourceforge.net/wiki/index.php?title=Category:En_author_Sharondippity . Second, this catalog is getting so large that maintaining the theme catalog is becoming a core. It looks like it is about time to replace the hand maintained page with the category page http://phpwebsite-comm.sourceforge.net/wiki/index.php?title=Category:Third_Party_Themes_Other . Ahhh but I am waiting to do that until all the individual theme pages are categorized. I alluded to this maintenance problem in item 2. The advantage that this solution provides is a flexible database
