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 494]
uboot-gta01-1.2.0+svnnow-r4_37837828d89084879bee2f2b8c7c68d4695940df_0_1791-do_fetch
([EMAIL PROTECTED])
2. [Bug 476]
uboot-gta01-1.2.0+svnnow-r4_8048cdd56f04a756eeea4951f402bf5cc33785db_0_1764-do_fetch
([EMAIL PROTECTED])
3. [Bug 476] downloads.openmoko.org tarballs require git-1.4.4
or higher ([EMAIL PROTECTED])
4. [Bug 482] phone still consumes energy when powered off
([EMAIL PROTECTED])
5. [Bug 476] downloads.openmoko.org tarballs require git-1.4.4
or higher ([EMAIL PROTECTED])
6. Your Bugzilla buglist needs attention. ([EMAIL PROTECTED])
7. [Bug 503] New: openmokobugzilla link fails
([EMAIL PROTECTED])
8. [Bug 43] StatusBar (Footer) API
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=494
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
------- Additional Comments From [EMAIL PROTECTED] 2007-04-19 13:23 -------
These are duplicates of #476.
------- 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=476
------- Additional Comments From [EMAIL PROTECTED] 2007-04-19 13:26 -------
Okay I have looked into the issue and git-core 1.5 and 1.4.3 do not have a
compatible file format. For
uboot-gta the file is fetched from wget
http://downloads.openmoko.org/sources/git_www.denx.de.git.u-
boot.git..tar.gz
If you untar it and issue git pull depending on your version of git-core you
will see:
fatal: corrupted pack file
.git/objects/pack/pack-a146bcbc18f4826d6bf2a7f63be5dd77bbb5b2f5.pack
Proposed resolution:
-Only create such tarballs with the minimum version of git required.
-Remove the tarball
-Require git 1.5 and find a package for debian stable to install on the
autobuilder
------- 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=476
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
Summary|uboot-gta01-1.2.0+svnnow- |downloads.openmoko.org
|r4_8048cdd56f04a756eeea4951f|tarballs require git-1.4.4
|402bf5cc33785db_0_1764- |or higher
|do_fetch |
------- Additional Comments From [EMAIL PROTECTED] 2007-04-19 14:35 -------
JFYI: the version difference was actually 1.4.4 and 1.4.3.
Removing the tarball is not really an option, since they get automatically
publicized there. This would mean that we'd have to have some blacklist of
files, maintained manually, that can not be put on downloads.openmoko.org
so while i'm not happy with it, the current solution was to update to git-1.4.4
on buildhost-old.openmoko.org (the autobuilder).
Leaving this bug open until we see better solutions coming up.
------- 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=482
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
Component|kernel |Audio
Product|OpenMoko |Neo1973 Hardware
Version|unspecified |GTA01Bv3
------- Additional Comments From [EMAIL PROTECTED] 2007-04-19 16:10 -------
mh, thinking a bit about how our power-off works (sending shutdown command to
PMU), I could think the audio amplifier LM4857 could still be "alive":
This component is powered directly by the battery. We might not power it down
completely before software issues power-off, resulting in some remaining power
draw by the amplifier. Unfortunately there seems to be no series resistor
between VDD of the LM4857 and +VB. Maybe the hardware team has an idea on how
to measure LM4857 power consumption?
------- 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=476
------- Additional Comments From [EMAIL PROTECTED] 2007-04-19 19:51 -------
I have restarted the autobuilds after conforming that the installed version
(1.4.4.3) is able to pull.
------- 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=204
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=301
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=340
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=379
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=408
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=412
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=422
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=503
Summary: openmokobugzilla link fails
Product: Site Infrastructure
Version: unspecified
Platform: Other
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Bugzilla
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
CC: [email protected]
The "openmokobugzilla" logo link at the top left links to
http://bugzilla.openmoko.org/cgi-bin/bugzilla/ which gives this error:
Forbidden
You don't have permission to access /cgi-bin/bugzilla/ on this server.
------- 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=43
------- Additional Comments From [EMAIL PROTECTED] 2007-04-20 11:07 -------
I think that using dbus for this is completely overkill. When you send a message
on the bus every process on the bus is woken up resulting in a context switch.
A much nicer solution I think would be to use X properties to convey this
information. This should give much better performance especially if a lot of
updates are being made (e.g. updating a progress bar.)
I'm going to spend some time today and tomorrow working on this. Another thing
that we could do is allow the process to use xembed (via GtkPlug/GtkSocket) to
embed a widget of their own choosing.
I know on the desktop the status notification area uses dbus however that needs
to receive messages from processes without an X window, from my understanding of
the purpose of the footer there will always be an X window for the process that
wants to control the panel
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
