Init scripts in Freemantle
I notice from http://wiki.maemo.org/Task:Maemo_roadmap/Fremantle#System_SW that the Location and format of init scripts differ. Since my ports of MySQL and Apache will require init scripts I need to make sure I install them in the right place and make whatever changes are necessary to the scripts themselves, but I haven't succeeded in finding any more information about this. Does anybody know where this can be found? It's odd that despite what's said about init script location, they still seem to be in the same place in the Maemo 5 SDK beta... -- Tony Green Ipswich, Suffolk, England http://www.beermad.org.uk/ http://www.suffolkcamra.co.uk/pubs/ * No Micro$oft products were used in the generation of this communication ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Init scripts in Freemantle
Hi On Sun, May 3, 2009 at 2:37 PM, Tony Green ma...@beermad.org.uk wrote: I notice from http://wiki.maemo.org/Task:Maemo_roadmap/Fremantle#System_SW that the Location and format of init scripts differ. Since my ports of MySQL and Apache will require init scripts I need to make sure I install them in the right place and make whatever changes are necessary to the scripts themselves, but I haven't succeeded in finding any more information about this. Does anybody know where this can be found? Last time I checked upstart 0.3.9 was used. http://upstart.ubuntu.com/wiki/Stanzas is the best available documentation greetings It's odd that despite what's said about init script location, they still seem to be in the same place in the Maemo 5 SDK beta... -- Tony Green Ipswich, Suffolk, England http://www.beermad.org.uk/ http://www.suffolkcamra.co.uk/pubs/ * No Micro$oft products were used in the generation of this communication ___ 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: Problem with the Diablo autobuilder
Hi, The autobuilder doesn't seem to be moving packages to extras-devel. I uploaded python-vte to the diablo autobuilder and it still has not shown up yet. I checked with some other packages, by other people, osm2go and dialcentral and they haven't been uploaded to extras-devel - despite it having been many hours since they had been uploaded. Please don't tell me to reupload as I do not have the original source packages available to me and the autobuilder, being the clever thing it is, deletes the source packages it has while it's moving them to extras-devel. I realise my tone isn't a nice one and the annoyance isn't directed at you, or the maemo.org team responisble for the autobuilder, but rather at the autobuilder for chewing my packages. Best Regards, Faheem On Thu, Apr 30, 2009 at 10:05 AM, Jeremiah Foster jerem...@jeremiahfoster.com wrote: On Apr 30, 2009, at 8:57, Cornelius Hald wrote: Hi, it looks like there is something wrong with the Diablo autobuilder. I was submitting conboy 0.3.2 two times already and it doesn't show up in extras-devel. For Chinook and Fremantle it worked fine. The mails I received are attached. It would be nice if someone please could check. As far as the autobuilder is concerned, the indexing tool that updates the list of Packages stopped running yesterday. I am trying to fix that now so that new packages start appearing in diablo. Jeremiah ___ 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: QA from extras-devel to extras-testing
On Apr 30, 2009, at 21:46, Andrew Zabolotny wrote: From Thu, 30 Apr 2009 12:13:33 +0300 Quim Gil quim@nokia.com wrote: The question is how to check and enforce them. What can be automated and what can be evaluated via testers feedback. Since Maemo is a community project, QA could be done by the community as well. As I see it, some person (or all developers?) is made part of the QA team; then, when a developer uploads a package to the autobuilder and he thinks it's ready for extras it marks the package somehow as ready (instead of pushing it directly, like now). Then the QA team members can look somehow at the list of ready packages and test any of them. After they test a package, they may vote somehow their opinion (with a optional field where they can go into details what they like/didn't). If package gets at least one negative vote, it's out of the queue for extras. If package gets, say, 10 positive votes (the number is to be determined experimentally), it's automatically moved to extras. Promotion from extras-devel to extras should be based on technical merit only. Voting will only lead to the type of acrimony we have already seen on this list and is structurally unfair. The QA process should involve anyone willing to participate, hopefully with many community members testing packages, but also Nokia being involved as well. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QA from extras-devel to extras-testing
On May 1, 2009, at 15:06, Matan Ziv-Av wrote: On Thu, 30 Apr 2009, Quim Gil wrote: What we shouldn't do is to create extras-testing or extras and let packages jump in without the QA process in place. Taking a buggy package out because of a new policy is going to be much more complicated. Let's see: Just a few months ago there was a great effort to close external repositories and move everything to extras repositrory. Extras repository was open for everyone. Now you suddenly change the rules and ask developers to jump thru who knows how many hoops to get packages to extras. That does not improve my confidence in the way Nokia manages maemo. Matan, we are working hard to make sure that maemo.org is open to everyone, users and developers. There are not going to be any rule changes, hopefully just some mechanisms to improve the quality of packages so that end users can rest assured that if they install something from extras they will not have to re-flash their tablet. I think you would agree that is reasonable and fair. How about leaving extras as is, and setting up a new repository called nokia_approved_applications_if_you_install_packages_from_another_repository_the_world_will_end where you do whatever QA you want to do. I assure you that the repositories are going to be an excellent place for your software. Nokia and maemo.org are really committed to doing the best for users and for developers and I really feel strongly about that - that is not just lip service. Regards, Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: QA from extras-devel to extras-testing
On May 2, 2009, at 16:11, Glen Ditchfield wrote: On Thu, 2009-04-30 at 22:53 -0400, Ryan Abel wrote: Assuming the package has a bug tracker, sure. On Saturday 02 May 2009 08:14:35 Murray Cumming wrote: That seems like a good requirement in general. If packages don't have to have bug trackers, then QA will have to build some infrastructure to keep track of positive and negative votes, and the packager's comments on the negative votes, and declarations that the problems that caused the negative votes have been fixed ... maybe it would be easier to require that packages have bug trackers, and use them for QA? Who is going to build all of this infrastructure? Won't this type of requirement help create separate private repos? Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Problem with the Diablo autobuilder
On May 3, 2009, at 18:52, Faheem Pervez wrote: Hi, The autobuilder doesn't seem to be moving packages to extras-devel. I uploaded python-vte to the diablo autobuilder and it still has not shown up yet. I checked with some other packages, by other people, osm2go and dialcentral and they haven't been uploaded to extras- devel - despite it having been many hours since they had been uploaded. Please don't tell me to reupload as I do not have the original source packages available to me and the autobuilder, being the clever thing it is, deletes the source packages it has while it's moving them to extras-devel. I realise my tone isn't a nice one and the annoyance isn't directed at you, or the maemo.org team responisble for the autobuilder, but rather at the autobuilder for chewing my packages. I understand Faheem, this is sub-optimal. I will look into it to try and stop this type of thing from happening. I will also look at why the autobuilder is not triggering the re-indexing. I will re-index by hand tonight. Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Maemo Official Platform Bug Jar 2009.18
A Quick Look at Maemo Official Platform in Bugzilla (https://bugs.maemo.org/). 2009-04-27 through 2009-05-03 As of 2009-05-04 Maemo Official Platform contains 1794 items (+22 this week), including 301 open issues (+9 this week): * 192 open bugs (+8 this week) * 5 critical/blocker (+1 this week) * 4 easyfix (no change this week) * 24 moreinfo (-5 this week) * 5 crash (+1 this week) * 8 patch (no change this week) * 8 reopened (no change this week) * 37 unconfirmed (+2 this week) * 109 open enhancements (+1 this week) * 2 easyfix (no change this week) * 4 moreinfo (-1 this week) * 2 patch (no change this week) * 2 reopened (no change this week) * 5 unconfirmed (+1 this week) ==--- New Items ---== 19 bugs were opened - ( https://bugs.maemo.org/buglist.cgi?bug_id=4387,4391,4393,4394,4396,4398,4399,4401,4402,4405,4406,4409,4410,4421,4422,4423,4439,4446,4450 ): * [4387] hd_status_plugin_item_set_status_area_icon() pixbuf documentation * [4391] part of the multimedia components docs blacked out * [4393] Stray markup elements * [4394] Code samples are shown on gray background * [4396] HIldon Tutorial has GNOME license boiler-plate * [4398] Hildon Tutorial mentions osso-af-settings instead of libhildondesktop-1 * [4399] OssoAddressBook API reference missing functions * [4401] Hildon HIG does not specify button ordering * [4402] Section 3.4.1 in the Hildon HIG is inconsistent * [4405] Hildon HIG needs native speaker review * [4406] Hildon HIG should suggest API * [4409] Hildon HIG: How do Information Notes and Banners differ * [4410] osso-system-lock-l10n-public has no source package * [4421] Invalid first line in maemo-scratchbox-install_5.0beta.sh * [4422] maemo-scratchbox-install_5.0beta.sh ignores -F argument * [4423] qemu: uncaught target signal 6 (aborted) core dumped * [4439] No way to choose a Desktop Widget * [4446] OProfile doc - kernel location for oprofile is wrong * [4450] libhildonfm2-dev lacks hildon-file-system-*.h header files 0 bugs were critical/blocker. 3 enhancements were opened - ( https://bugs.maemo.org/buglist.cgi?bug_id=4404,4420,4453 ): * [4404] HIG should show screenshots * [4420] Better GUI design guidelines * [4453] PPTP and L2TP support out of the box could be good idea. ==--- Resolved Bugs ---== 6 bugs were resolved fixed - ( https://bugs.maemo.org/buglist.cgi?bug_id=1045,4341,4393,4394,4410,4421 ): * [1045] Media player breaks the original sorting of songs in a CD * [4341] Can't use hildon_banner_show_information() in home applet. (FiF) * [4393] Stray markup elements * [4394] Code samples are shown on gray background * [4410] osso-system-lock-l10n-public has no source package * [4421] Invalid first line in maemo-scratchbox-install_5.0beta.sh --- (FiF) indicates the bug is Fixed in Fremantle. 2 bugs were resolved invalid - ( https://bugs.maemo.org/buglist.cgi?bug_id=4391,4423 ): * [4391] part of the multimedia components docs blacked out * [4423] qemu: uncaught target signal 6 (aborted) core dumped 3 bugs were resolved wontfix - ( https://bugs.maemo.org/buglist.cgi?bug_id=1685,2474,4038 ): * [1685] uppercase (sliding upstroke) on vkb (Virtual keyboard) doesn't work as well with 4.2007 as 3.2007 * [2474] Shift-space on BT keyboard disables virtual keyboard, requires reboot * [4038] VKB doesn't provide ShiftKP_Enter 0 bugs were resolved duplicate. 0 bugs were resolved worksforme. 0 bugs were resolved moved. ==--- Resolved Enhancements ---== 0 enhancements were resolved fixed. 0 enhancements were resolved invalid. 2 enhancements were resolved wontfix - ( https://bugs.maemo.org/buglist.cgi?bug_id=2467,4380 ): * [2467] Add support for modifier keys. * [4380] Publish sources of gpsdriver and libsupld 0 enhancements were resolved duplicate. 0 enhancements were resolved worksforme. 0 enhancements were resolved moved. ==--- Confirmed Items ---== 4 bugs were confirmed - ( https://bugs.maemo.org/buglist.cgi?bug_id=3144,4180,4402,4422 ): * [3144] Device starts reboot loop when charging * [4180] very slow clutter performance * [4402] Section 3.4.1 in the Hildon HIG is inconsistent * [4422] maemo-scratchbox-install_5.0beta.sh ignores -F argument 2 enhancements were confirmed - ( https://bugs.maemo.org/buglist.cgi?bug_id=4380,4420 ): * [4380] Publish sources of gpsdriver and libsupld * [4420] Better GUI design guidelines ==--- Reopened Items ---== 0 bugs were reopened. 0 enhancements were reopened. ==--- Unloved Items ---== 4 bugs were needing love - ( https://bugs.maemo.org/buglist.cgi?bug_id=4187,4446,4209,4450 ): * [4187] Autoconf should be replaced by configure in one paragraph * [4446] OProfile doc - kernel location for oprofile is wrong * [4209] two key mappings for iGo bluetooth keyboard reverse upon connection timeout * [4450] libhildonfm2-dev lacks hildon-file-system-*.h header files 1 enhancement was needing love - (
