THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#215 - Kingston 32GB Class6G2 SDHC card not working in pandora
User who did this - Michael Mrozek (EvilDragon)
----------
Please try again with latest Kernel 3.2 (SuperZaxxon Beta 3), as it supports more cards.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=215#comment377
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has been changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab.
FS#255 - Waking Pandora with closed lid nevertheless turns screen on
User who did this: Michael Mrozek (EvilDragon)
Percent Complete: 0% -> 100%
Due in Version: [-] -> SuperZaxxon Beta 4
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=255
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#279 - pidgin requires (more) locales to work correctly
User who did this - Michael Mrozek (EvilDragon)
----------
Added to recipe for SuperZaxxon Beta 4.
Needs testing.
----------
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=279#comment376
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has been changed. The changes are listed below. For full information about what has changed, visit the URL and click the History tab.
FS#279 - pidgin requires (more) locales to work correctly
User who did this: Michael Mrozek (EvilDragon)
Percent Complete: 0% -> 100%
Due in Version: [-] -> SuperZaxxon Beta 4
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=279
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Nils Kneuper (Ivanovic)
Attached to Project - OpenPandora Main OS
Summary - pidgin requires (more) locales to work correctly
Task Type - Feature Request
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - Release 1 (Zaxxon)
Severity - Medium
Priority - Normal
Reported Version - Hotfix 6
Due in Version - Undecided
Due Date - Undecided
Details - Please add the following package to allow umlauts working in pidgin:
glibc-gconv-utf-16
After installing this package I no longer have a problem receiving umlauts in pidgin. Besides it might also make sense to add "glibc-gconv-cp1250" which might be required for western europe and koi8-r which seems to be missing for xchat and conversion of chars there.
At the moment the following locale related packages are installed (as of SuperZaxxon Beta3):
glibc-charmap-utf-8 - 2.9-r35.3.5
glibc-gconv - 2.9-r35.3.5
glibc-gconv-cp1252 - 2.9-r35.3.5
glibc-gconv-ibm850 - 2.9-r35.3.5
glibc-gconv-iso8859-1 - 2.9-r35.3.5
glibc-gconv-iso8859-15 - 2.9-r35.3.5
Please add:
glibc-gconv-cp1250
glibc-gconv-koi8-r
glibc-gconv-unicode
glibc-gconv-utf-16
Thanks!
More information can be found at the following URL:
http://bugs.openpandora.org/index.php?do=details&task_id=279
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Branch: refs/heads/master
Home: https://github.com/openpandora/meta-openpandora
Commit: f76609fd8f961be21e8af811ad85ba3a958c1faa
https://github.com/openpandora/meta-openpandora/commit/f76609fd8f961be21e8a…
Author: David-John Willis <John.Willis(a)Distant-earth.com>
Date: 2012-04-12 (Thu, 12 Apr 2012)
Changed paths:
A recipes-graphics/xorg-xserver/xserver-xf86-config/omap3-pandora/xorg.conf.d/10-evdev.conf
R recipes-graphics/xorg-xserver/xserver-xf86-config/omap3-pandora/xorg.conf.d/10-omapfb.conf
A recipes-graphics/xorg-xserver/xserver-xf86-config/omap3-pandora/xorg.conf.d/20-omapfb.conf
M recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
Log Message:
-----------
xserver-xf86-config: Fix silly schoolboy error.
* I forgot to add the machine to SRC_URI_append
when adding xorg.conf.d support so broke any
other BSP that also used xorg.conf.d by forcing
it to look for this BSP's files.
Bad John!
Looks like someone found an ABI problem, where one of the libpnd
structs changed and possibly breaks dependant applications. In the end I'm
not sure if it was a problem for him, but it looks like a problem others
may run into.
A struct member was patched in near the top of pnd_disco_t (return
from the pnd auto discovery routine, one of the main routines libpnd users
depend on), rather than at the end of the struct. Usually I catch this
sort of patch change and push it to the end of the struct instead ..but
that one slipped through the cracks I'm afraid.
http://git.openpandora.org/cgi-bin/gitweb.cgi?p=pandora-libraries.git;a=blo…
The problem we have is this patch came in back in May or so, so
itself has been around awhile; ie: anyone building against current libpnd
for thelast few months has _that_ ABI, while older apps might use the
original ABI. Were it a recent patch, a decision is easier :)
So I'm on the fence.. do we move the struct member to the end so
as to 'right it', or do we leave it as is since we'ev been here for
awhile.
Risks either way, as we have no idea how many apps are using pre-
and post- patch struct :/
At this point, its probably best to just sit on it, as some devs
may have handled the ABI change themselves (if version foo do it thusly,
otherwise thatly) and further changes may just mess things up
more/again....
Any opinions on the matter?
jeff
--
If everyone would put barbecue sauce on their food, there would be no war.