[Debian-olpc-devel] lenny (debian.jones.dk) tests
dr at jones.dk
Tue Nov 10 17:18:25 UTC 2009
On Tue, Nov 10, 2009 at 05:28:16PM +0100, Sascha Silbe wrote:
>On Tue, Nov 10, 2009 at 02:01:44PM +0100, Jonas Smedegaard wrote:
>>Yes, I have noticed this as well. Please do file a bugreport
>>against sugar-0.84,sugar-0.86 (i.e. against both of them at the
>Will "Package: sugar-0.84,sugar-0.86" do the right thing? The
>instructions  don't mention anything, neither does any other page
>I looked at.
Yes, that should work.
You can double-check afterwards (after a little while) if it properly
shows at http://bugs.debian.org/sugar-0.84 and
http://bugs.debian.org/sugar-0.86 - if it doesn't then the bugreport
isn't all lost: you receive an acknowledgement that contains the bug
number - tell me that number and I'll help fork and reassign to both
packages (or try do it yourself if you like the challenge). :-)
>>>The usual Xephyr issues (broken keymap) appear.
>>Please elaborate: I am unsure what "usual" Xephyr issues you are
>SL #342 / Xephyr #19365 [2-3], SL #1075 .
>In short: Keymap is incorrect and shortcuts don't work.
Thanks for the pointers. Would be nice to have these user-visible
issues visible to Debian users too. So please do file bugreports at the
Debian BTS about them, referring to the upstream issues.
I can do it too, but I have plenty of things on my hand already, so
would really appreciate help with this.
>>>line 318, in _monitor_connection
>>> File "/usr/lib/python2.5/site-packages/telepathy/client/interfacefactory.py",
>>Please tell me which version of sugar-0.84 you have tested against:
>root at aquarium:~# dpkg -l sugar-0.84
>|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
>||/ Name Version
>ii sugar-0.84 0.84.6-12~0jones1
But wait: Are you testing on a fullblown system or inside a chroot?
If in a chroot then how much did you duplicate from the outside system?
E.g. when not using network-manager then /etc/network/interfaces may be
relevant - or perhaps it instead is bind-mounted /proc and /sys that
needs to be there in order for chroot'ed network tools to properly
report the active network devices.
If in a chroot then perhaps DBus accidentally use network sockets
instead of file-based sockets and talks to the outside system?
All in all, this might be completely independent to backport to Lenny,
and instead be an issue related to your way of testing it. Perhaps try
testing similarly a Sid system?
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: Digital signature
More information about the Debian-olpc-devel