Send buglog mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:

   1. [Bug 605] New: initscripts not compatible to busybox
      ([EMAIL PROTECTED])
   2. [Bug 587] Icon-theme broken since settings-daemon integration
      ([EMAIL PROTECTED])
   3. [Bug 604] DFU at bootdelay conflicts with normal boot nand
      read ([EMAIL PROTECTED])
   4. [Bug 602] Python extensions not getting installed
      ([EMAIL PROTECTED])
   5. [Bug 602] Python extensions not getting installed
      ([EMAIL PROTECTED])
   6. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=605

           Summary: initscripts not compatible to busybox
           Product: OpenMoko
           Version: current svn head
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: sysinit
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]
                CC: [email protected]


The initscripts (i was trying xserver-nodm stop) are using arguments which are
not present in the busybox implementation (/bin/ps: invalid option -- e)



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=587

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2007-06-13 12:22 -------
Appears to be reliably fixed now



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=604

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[EMAIL PROTECTED]



------- Additional Comments From [EMAIL PROTECTED]  2007-06-13 12:42 -------
As a workaround, you could just bring up the boot menu (by holding down
AUX while u-boot starts). That keeps the system from autobooting. DFU
subsequently disables the idle timeout of the boot menu itself.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=602

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|[EMAIL PROTECTED]     |[EMAIL PROTECTED]



------- Additional Comments From [EMAIL PROTECTED]  2007-06-13 21:31 -------
I just tried your recipe. Adding it to task-openmoko and bumping the PR works
fine here. Python and your module will be installed in the rootfs.

/usr/lib/python2.4/site-packages/pymoko.so

The attached patch is my svn diff. Just your recipe with a SRC_URI change for
the tarball and the changes to task-openmoko.

Please try the following:

1. Revert your own changes to svn, backup before, add my patch and test
2. Completely remove the tmp dir under oe/build and start the build from 
scratch.



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=602





------- Additional Comments From [EMAIL PROTECTED]  2007-06-13 21:32 -------
Created an attachment (id=189)
 --> 
(http://bugzilla.openmoko.org/cgi-bin/bugzilla/attachment.cgi?id=189&action=view)
Add pymoko to buildsystem




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.



--- End Message ---
--- Begin Message ---
[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Bugzilla 
bugsystem (http://bugzilla.openmoko.org/cgi-bin/bugzilla/) that require
attention.

All of these bugs are in the NEW state, and have not been touched
in 7 days or more.  You need to take a look at them, and 
decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to someone
    else.  (Hint: if you don't know who to reassign it to, make sure that
    the Component field seems reasonable, and then use the "Reassign bug to
    owner of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW bugs, you can use this URL (bookmark it if you like!):

    
http://bugzilla.openmoko.org/cgi-bin/bugzilla/buglist.cgi?bug_status=NEW&[EMAIL 
PROTECTED]

Or, you can use the general query page, at
http://bugzilla.openmoko.org/cgi-bin/bugzilla/query.cgi.

Appended below are the individual URLs to get to all of your NEW bugs that 
haven't been touched for a week or more.

You will get this message once a day until you've dealt with these bugs!

  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=69
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=70
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=112
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=114
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=137
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=141
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=181
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=412
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=422
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=448
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=470
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=471
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=536
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=540
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=541
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=555
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=572
  http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=589



--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog

Reply via email to