Re: Making a custom root FS
D. Scott Brown wrote: 3. extract the rootfs from the retail image, mount it, and tar it. If I mount the JFFS2 using kernel memory emulating a MTD, I get error inserting mtdram - cannot allocate memory. If I mount the JFFS2 using block device emulating MTD, the tar fails with tons of read errors at byte 0. Check script and folowup posts here http://www.internettablettalk.com/forums/showthread.php?p=192475#post192475 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
[Mono] question about mono install and selinux
Hi, I've experimented an error after installed mono on maemo-scratchbox. Starting from a clean maemo dev environment, i've followed the instruction present at http://maemo.org/community/wiki/mono/. Running mono i get the following error: /scratchbox/devkits/mono/bin/mono: error while loading shared libraries: libselinux.so.1: cannot open shared object file: No such file or directory And ldd says to me: ldd /scratchbox/devkits/mono/bin/mono /scratchbox/tools/lib/libsb.so.0 = /scratchbox/tools/lib/libsb.so.0 (0xb7f3e000) libc.so.6 = /scratchbox/host_shared/lib/libc.so.6 (0xb7e0b000) libdl.so.2 = /scratchbox/host_shared/lib/libdl.so.2 (0xb7e08000) libsb_env.so.0 = /scratchbox/tools/lib/libsb_env.so.0 (0xb7e06000) /scratchbox/host_shared/lib/ld.so = /scratchbox/host_shared/lib/ld.so (0xb7f49000) Seems that mono didn't link directly to selinux, anybody has same suggestion?! Thanks in advance Andrea ___ Scopri il Blog di Yahoo! Mail: trucchi, novità, consigli... e la tua opinione! http://www.ymailblogit.com/blog/___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Rebuild all chinook source packages on autobuilder
Ed Bartosh a écrit : On Wed, 2008-06-18 at 18:00 +0200, ext Fred wrote: That's because you haven't promote your packages to extras. Autobuilder puts successfully built packages into extras-devel. It's up to package maintainer to decide when package is ready to be promoted from extras-devel to extras. This is what promotion interface was made for [1]. [1] https://garage.maemo.org/promoter-beta/interface.py [snip] Does should the promoter work or it isn't functional yet? Theoreticaly it should work. However we didn't get any feedback about it since it was announced several months ago, so I can't say for sure. I tried it again yesterday (contactinfos, phonelink; gnokii, gnokii-gconf) and it looks like it didn't change anything ... It should work now. We fixed it 2 days ago. Please let me know if you still experience problems using it. Regards, -- Ed What delay should I expect before the promotion is made ? I tried again an hour ago but cannot see any differences when I check the page ( https://garage.maemo.org/promoter-beta/interface.py ) Fred ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Rebuild all chinook source packages on autobuilder
On Mon, 2008-06-23 at 11:52 +0200, ext Fred wrote: Ed Bartosh a écrit : On Wed, 2008-06-18 at 18:00 +0200, ext Fred wrote: That's because you haven't promote your packages to extras. Autobuilder puts successfully built packages into extras-devel. It's up to package maintainer to decide when package is ready to be promoted from extras-devel to extras. This is what promotion interface was made for [1]. [1] https://garage.maemo.org/promoter-beta/interface.py [snip] Does should the promoter work or it isn't functional yet? Theoreticaly it should work. However we didn't get any feedback about it since it was announced several months ago, so I can't say for sure. I tried it again yesterday (contactinfos, phonelink; gnokii, gnokii-gconf) and it looks like it didn't change anything ... It should work now. We fixed it 2 days ago. Please let me know if you still experience problems using it. What delay should I expect before the promotion is made ? I tried again an hour ago but cannot see any differences when I check the page ( https://garage.maemo.org/promoter-beta/interface.py ) Which packages did you try to promote? After it was fixed on Friday I at least managed to promote several packages (db4.2, libwww and couple of others). Regards, Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community council
On Mon, 2008-06-16 at 22:13 +0200, Dave Neary wrote: Hi all, So - the community council, then... what do people think of the idea? I like it. It's not clear what it will become, but it could be a good way for Maemo to start becoming less owned by Nokia alone, thus giving it more life. I think Nokia want to have way to do this. I recommend being quite informal to start with, only adding rules and bureaucracy where it's genuinely useful. What should the remit be? At the very least it can be a group of people who's job it is to clearly and briefly express the community's needs and concerns. Where consensus exists, it should express it. The mailing list is too busy for most people to see that otherwise. Like the GNOME Board, it may later wish to delegate some tasks to specialized groups, such as administrators for mailing lists, web servers, source code repositories, etc. I agree with the poster who said that monthly or quarterly election would be too frequent. All depends on how onerous the voting process will be, I suppose. Proposals to go here: https://wiki.maemo.org/Task:Community_Council And discussions can go to the list, or here: https://wiki.maemo.org/Talk:Task:Community_Council -- [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community council
ext Murray Cumming wrote: On Mon, 2008-06-16 at 22:13 +0200, Dave Neary wrote: Hi all, So - the community council, then... what do people think of the idea? I like it. It's not clear what it will become, but it could be a good way for Maemo to start becoming less owned by Nokia alone, thus giving it more life. I think Nokia want to have way to do this. Yes, Nokia finds this proposal an interesting step forward. Same opinions and concerns: start easy, define a flexible model to be evolved, no unnecessary bureaucracy... Proposals to go here: https://wiki.maemo.org/Task:Community_Council And discussions can go to the list, or here: https://wiki.maemo.org/Talk:Task:Community_Council -- Quim Gil marketing manager, open source Maemo Software @ Nokia ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Rebuild all chinook source packages on autobuilder
Ed Bartosh a écrit : On Mon, 2008-06-23 at 11:52 +0200, ext Fred wrote: Ed Bartosh a écrit : On Wed, 2008-06-18 at 18:00 +0200, ext Fred wrote: That's because you haven't promote your packages to extras. Autobuilder puts successfully built packages into extras-devel. It's up to package maintainer to decide when package is ready to be promoted from extras-devel to extras. This is what promotion interface was made for [1]. [1] https://garage.maemo.org/promoter-beta/interface.py [snip] Does should the promoter work or it isn't functional yet? Theoreticaly it should work. However we didn't get any feedback about it since it was announced several months ago, so I can't say for sure. I tried it again yesterday (contactinfos, phonelink; gnokii, gnokii-gconf) and it looks like it didn't change anything ... It should work now. We fixed it 2 days ago. Please let me know if you still experience problems using it. What delay should I expect before the promotion is made ? I tried again an hour ago but cannot see any differences when I check the page ( https://garage.maemo.org/promoter-beta/interface.py ) Which packages did you try to promote? After it was fixed on Friday I at least managed to promote several packages (db4.2, libwww and couple of others). Regards, Ed Thanks a lot : It worked ! (I should have been more patient) ;) It promoted for me : contactinfos, gnokii, gnokii-gconf, grcm and phonelink Thanks Fred ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Rebuild all chinook source packages on autobuilder
On Mon, 2008-06-23 at 14:07 +0200, ext Fred wrote: Theoreticaly it should work. However we didn't get any feedback about it since it was announced several months ago, so I can't say for sure. I tried it again yesterday (contactinfos, phonelink; gnokii, gnokii-gconf) and it looks like it didn't change anything ... It should work now. We fixed it 2 days ago. Please let me know if you still experience problems using it. What delay should I expect before the promotion is made ? I tried again an hour ago but cannot see any differences when I check the page ( https://garage.maemo.org/promoter-beta/interface.py ) Which packages did you try to promote? After it was fixed on Friday I at least managed to promote several packages (db4.2, libwww and couple of others). Regards, Ed Thanks a lot : It worked ! (I should have been more patient) ;) It promoted for me : contactinfos, gnokii, gnokii-gconf, grcm and phonelink Thank you for your feedback! If you have any ideas about promoter, don't hesitate to share them here. We haven't got much feedback about it. Frankly we almost haven't got any :) Regards, --- Ed ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Sardine is dead.
Hi, I am sorry to announce that the 'unstable' Sardine distribution of the Hildon Desktop is dead. It's corpse is being removed: the buildbot will be shut down, and the repositories will be removed from the servers. We didn't manage to make it useful enough to justify keeping it alive. Of course, the source code of the packages that have been built for Sardine continues to be developed in real-time in the open, and you can in fact expect more projects to be freed over time. Most of the projects are developed on stage.maemo.org: https://stage.maemo.org/svn/maemo/projects/haf/trunk/ Should anyone be interested, the Sardine machinery is hosted in the maemo garage: https://garage.maemo.org/projects/sardine/ So long, and thanks for all the fish! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Rebuild all chinook source packages on autobuilder
Ed Bartosh a écrit : On Mon, 2008-06-23 at 14:07 +0200, ext Fred wrote: Theoreticaly it should work. However we didn't get any feedback about it since it was announced several months ago, so I can't say for sure. I tried it again yesterday (contactinfos, phonelink; gnokii, gnokii-gconf) and it looks like it didn't change anything ... It should work now. We fixed it 2 days ago. Please let me know if you still experience problems using it. What delay should I expect before the promotion is made ? I tried again an hour ago but cannot see any differences when I check the page ( https://garage.maemo.org/promoter-beta/interface.py ) Which packages did you try to promote? After it was fixed on Friday I at least managed to promote several packages (db4.2, libwww and couple of others). Regards, Ed Thanks a lot : It worked ! (I should have been more patient) ;) It promoted for me : contactinfos, gnokii, gnokii-gconf, grcm and phonelink Thank you for your feedback! If you have any ideas about promoter, don't hesitate to share them here. We haven't got much feedback about it. Frankly we almost haven't got any :) Regards, --- Ed The main remark I would have about it is : Why should I be able to promote package I didn't upload ... I know it may not be easy but as we are required to login with our garage account would it not be possible to restrict the view to project that we are maintainer of ? Fred ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community council
Hi, (in plain text, as requested) Murray said below: I like it. It's not clear what it will become, but it could be a good way for Maemo to start becoming less owned by Nokia alone, thus giving it more life (signature by Quim, from other message) Quim Gil marketing manager, open source Maemo Software @ Nokia I really don't like the idea of anything being less or more owned. Maemo is project by Nokia, Maemo.org website is owned by Nokia, development is supported, financed by Nokia, some developers are donated by Nokia, so what is your idea of having third party owners to Maemo or transferring some rights to Maemo to third parties ? To me Maemo= Nokia. Community council can't change anything in Maemo ownership rights as council has no legal title to transfer any rights in Maemo. So suggesting otherwise makes no sense. Closing. Maemo=Nokia and community council is ok for Nokia and for the community as maemo can not be incorporated by initial directors as already owned by Nokia. If you are aware of any maemo software based embedded device, made by other corporation than Nokia, please let me know. Darius --- On Mon, 23/6/08, Murray Cumming [EMAIL PROTECTED] wrote: From: Murray Cumming [EMAIL PROTECTED] Subject: Re: Community council To: Dave Neary [EMAIL PROTECTED] Cc: maemo-developers@maemo.org maemo-developers@maemo.org Date: Monday, 23 June, 2008, 1:31 PM On Mon, 2008-06-16 at 22:13 +0200, Dave Neary wrote: Hi all, So - the community council, then... what do people think of the idea? I like it. It's not clear what it will become, but it could be a good way for Maemo to start becoming less owned by Nokia alone, thus giving it more life. I think Nokia want to have way to do this. I recommend being quite informal to start with, only adding rules and bureaucracy where it's genuinely useful. What should the remit be? At the very least it can be a group of people who's job it is to clearly and briefly express the community's needs and concerns. Where consensus exists, it should express it. The mailing list is too busy for most people to see that otherwise. Like the GNOME Board, it may later wish to delegate some tasks to specialized groups, such as administrators for mailing lists, web servers, source code repositories, etc. I agree with the poster who said that monthly or quarterly election would be too frequent. All depends on how onerous the voting process will be, I suppose. Proposals to go here: https://wiki.maemo.org/Task:Community_Council And discussions can go to the list, or here: https://wiki.maemo.org/Talk:Task:Community_Council -- [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers Send instant messages to your online friends http://uk.messenger.yahoo.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Diablo extras repository proposal
Hi, ext Niels Breet wrote: It has been a while since we had a discussion about the future requirements of the extras repository. Since there haven't been any concrete proposals for what we can do for the short-term, I have made a proposal[1] on the wiki. With this proposal I am trying to push the repository reform. If we want change, we need to act. I would really appreciate it if you could look at this proposal and see if you like/dislike this. Remember that this proposal is for Diablo, the more ambitious plans [2] might be a goal for Fremantle. This also depends on your support to various parts of the process. Please discuss the proposal on this mailinglist or on the wiki discussion page[3]. --- o The autobuilder will do some really basic QA, basically it only checks if the package builds. o It will also prevent packages with broken dependencies from entering the repository. We might want to add more checks later, but don't want to make it impossible for new developers to upload packages. --- Even for extras-devel I would require that packages are also: - installable - removable Extras could then check that the package is also upgradable (at least from previous version). I guess autobuilder uses Sbox, so it would be checking installation against GNU utilities instead of the more restricted Busybox version that are on the device, but at least that's better than nothing. (If system Qemu starts working well enough, maybe testing installation could be done with it some time in the future...) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Diablo extras repository proposal
Hi, Hi, Even for extras-devel I would require that packages are also: - installable - removable I really like the idea, but I don't think that is feasible for Diablo. This should be added to the wiki page with all the more ambitious ideas[1]. For Fremantle this can probably be implemented. (Autotester?) Extras could then check that the package is also upgradable (at least from previous version). Sure, that sounds like a sensible thing to do. I guess autobuilder uses Sbox, so it would be checking installation against GNU utilities instead of the more restricted Busybox version that are on the device, but at least that's better than nothing. I'll let Ed answer this one :) (If system Qemu starts working well enough, maybe testing installation could be done with it some time in the future...) - Eero - Niels [1] https://wiki.maemo.org/Extras_repository_process_definition ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community council
Darius Jack wrote: [snip] Hi Darius In response to your previous email where you said: Please unsubscribe me from maemo-developers list as I am not interested in your fight for maemo comunity leadership. You may like to visit: https://lists.maemo.org/mailman/listinfo/maemo-developers Cheers David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Problem with quilt when rebuilding chinook package on autobuilder
The Chinook extras rebuild page [1] lists at least three packages that fail to rebuild because of problems with the quilt patch manager: libfont-ttf-perl, nfs-utils, and sdlpango. All three declare build-depends on quilt; all three attempt to include a file in their debian/rules file (/usr/share/quilt/quilt.make or /usr/share/cdbs/1/rules/patchsys-quilt.mk); all three builds fail because the file doesn't exist. quilt.make and patchsys-quilt.mk should be installed as part of the quilt package. They are both present in the scratchbox on my computer. I uploaded libfont-ttfperl directly to chinook-extras-builder, and it built successfully. The only difference that I know of is that the package I uploaded to chinook-extras-builder was built with dpkg-buildpackage -S -sa, while the package I uploaded to chinook-extras was built with dpkg-buildpackage -i. Is this a problem with the extras assistant, or is there some problem with libfont-ttf-perl that I can fix? [1] 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
problem with playing wav file
Hi,
I'm able to play the wav file by using gst-launch as fallows
gst-launch-0.10 filesrc location=~/songs/4voice.wav ! wavparse !
audioconvert ! alsasink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstAudioSinkClock
Caught interrupt -- handling interrupt.
Interrupt: Setting pipeline to PAUSED ...
Execution ended after 1914601000 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
FREEING pipeline ...
I modified the helloworld code to play the wav as
1. I created waveparse in place of oggdemux and vorbis parser elements
2. Added filesrc, waveparse and alsasink to the pipeline and linked.
--
int
main ( int argc, char *argv[] )
{
GMainLoop *loop;
GstBus *bus;
gst_init ( argc, argv );
loop = g_main_loop_new ( NULL, FALSE );
pipeline = gst_pipeline_new ( audio-player );
source = gst_element_factory_make ( filesrc, file-source );
//parser = gst_element_factory_make ( oggdemux, ogg-parser );
parser = gst_element_factory_make ( wavparse, wave-parser );
//decoder = gst_element_factory_make ( vorbisdec, vorbis-decoder
);
conv = gst_element_factory_make ( audioconvert, converter );
sink = gst_element_factory_make ( alsasink, alsa-output );
if ( !pipeline || !source || !parser || !conv || !sink ) {
g_print ( One element could not be created\n );
return -1;
}
g_object_set (G_OBJECT (source), location, argv[1], NULL );
bus = gst_pipeline_get_bus ( GST_PIPELINE ( pipeline ) );
gst_bus_add_watch ( bus, bus_call, loop );
gst_object_unref ( bus );
gst_bin_add_many ( GST_BIN ( pipeline), source, parser,
conv, sink, NULL );
//gst_element_link ( source, parser );
gst_element_link_many ( source, parser, conv, sink, NULL );
g_signal_connect ( parser, pad-added, G_CALLBACK ( new_pad ), NULL
);
g_print ( Setting to Playing\n );
gst_element_set_state ( pipeline, GST_STATE_PLAYING );
g_print ( Running\n );
g_main_loop_run ( loop );
g_print ( Returned, stopping playback\n );
gst_element_set_state ( pipeline, GST_STATE_NULL );
g_print ( Deleting pipeline\n );
gst_object_unref ( GST_OBJECT ( pipeline ) );
return 0;
}
--
When i tried to run the fallowing code, i'm getting fallowing errors
--
./a.out ~/songs/4voice.wav
Setting to Playing
Running
Dynamic pad created, linking parser/decoder
(a.out:20136): GStreamer-CRITICAL **: gst_element_get_static_pad: assertion
`GST_IS_ELEMENT (element)' failed
(a.out:20136): GStreamer-CRITICAL **: gst_pad_link_prepare: assertion
`GST_IS_PAD (sinkpad)' failed
(a.out:20136): GStreamer-CRITICAL **: gst_object_unref: assertion `object !=
NULL' failed
Error: Internal data flow error.
Returned, stopping playback
Deleting pipeline
--
Somebody already posted the similar problem in the mailing list (
http://lists.maemo.org/pipermail/maemo-developers/2006-August/023007.html ),
but solution is not mentioned over there.
It would be of great help if somebody look into this.
Thanks,
Ganesh
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community council
Well the only point that I agree that one problem here is that maybe people who would want to develop with Maemo can't sell it on their devices with the Maemo branding, as that is owned by Nokia. Unless Nokia gives rights to the commons so that anyone, including other companies, to use it on their devices (Which either for free or for some licensing fee is doable), then Nokia is still within rights to charge people for using their brand/trademark (an asset of the corporation). There are currently a number of open projects to create embedded device operating systems, and currently there are new manufacturers that are using Linux to drive their devices. So trademark rights issues get mushy here. Here's an interesting example: I'm a guy who wants to make a fork of all of the current embedded OSes to create my own super-OS. So I go looking and start blending software together, if someone's logo is on their that didn't want it there, they can sue me for damages. If I made a device that has a Meamo fork I call Maemo-is-dumb-don't-use-it. And if Nokia gets angry because that contributed to the decline in adoption of the platform, I could potentially be accountable in court. People really do sue for stupid things. If the software is indeed open then skinning tools need to be done in such a way for a manufacturer or some other project to switch in their logos. Which I think in the end is a prefered solution that the market will like. Companies like to have their own OS-wide branding that doesn't take away from the basic experience that most people have (in most cases this is Windows). That's definitely what Microsoft is banking on with their mobile os permeating the market. So yeah, there are some realistic things to consider, and negotiate out to gain wider support and adoption. I think it's good to create a value proposition that is understandable to manufacturers, developers, and people industry-wide so that they can feel confident in also contributing to Maemo, or whatever we want to call it, with ample rights secured so they know they are investing in a good solution. I hope this all makes sense, it's high-level communications and marketing stuff that you need to think about with regards to brand ownership, copyright, and other IP that businesses have exclusive rights to (unless stated elsewhere). Cheers, P On Mon, Jun 23, 2008 at 5:26 PM, David Greaves [EMAIL PROTECTED] wrote: Darius Jack wrote: [snip] Hi Darius In response to your previous email where you said: Please unsubscribe me from maemo-developers list as I am not interested in your fight for maemo comunity leadership. You may like to visit: https://lists.maemo.org/mailman/listinfo/maemo-developers Cheers David ___ 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
Installing xulrunner on N810
Hi, Hi, I have done the same as stated in http://blog.mozilla.com/blassey/2008/03/17/maemo-buildbot/ to install xulrunner on myN810 OS2008, except that i extracted xulrunner in /media/mmc2/, because i don't have much space in /opt. This doesn't work when i tried to run mybrowser-0.2.2.xulapp application. Nothing is there in /usr/lib/. Can someone help? Jitender ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Installing xulrunner on N810
Doesn't creating softlink to /media/mmc2 xulrunner work? -kwan On Mon, Jun 23, 2008 at 11:38 PM, jitender singh [EMAIL PROTECTED] wrote: Hi, Hi, I have done the same as stated in http://blog.mozilla.com/blassey/2008/03/17/maemo-buildbot/ to install xulrunner on myN810 OS2008, except that i extracted xulrunner in /media/mmc2/, because i don't have much space in /opt. This doesn't work when i tried to run mybrowser-0.2.2.xulapp application. Nothing is there in /usr/lib/. Can someone help? Jitender ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers -- http://www.media.mit.edu/~kwan/info.html ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
