Getting a SoaS Docs Effort off the Ground
by Sebastian Dziallas
From looking at the currently available documentation for Sugar on a
Stick, I think it makes sense to collaborate on writing well written
official instructions for it. So I've entered a Blueprint in Launchpad
on it: https://blueprints.launchpad.net/soas/+spec/better-docs-for-soas
I'd like to give the great Fedora Publican tool a try, as it has
recently seen a new beta release. I have set up a new GIT repo in
Gitorious, which lives here: http://git.sugarlabs.org/projects/soas-docs
So if you're interested in writing the next generation of totally
awesomeness-spreading SoaS docs, please speak up! :) ...you can even add
yourself already to the Launchpad page and apply for commit access to
the GIT repo, too.
--Sebastian
14 years, 8 months
Re: yum not accessing repository when running F12-on-XO1
by Peter Robinson
On Wed, Sep 9, 2009 at 12:12 PM, Mikus Grinbergs<mikus(a)bga.com> wrote:
> I'm going to assume my F12-on-XO1 yum problem was non-reproducible.
>
> I did a 'yum clean all', plus manually going into /var and removing things
> whose names started with "yum". After that, I was able to use the customary
> 'yum' commands with F12-on-XO1.
I've not seen any issues. You probably shouldn't remove all yum
directories within /var/. A 'yum clean all' is all I've ever needed to
do. The only directory you might wish to clean up is /var/cache/yum.
>> Is it trying to connect to the same mirror each time.
>> It could be issues with a particular mirror.
>
> Your answer is what motivated me to try to start over with a "clean slate".
>
> The catch is - I had no information whatever about what mirror it was trying
> to contact - no output from yum except for "could not retrieve". In my
> experience, when there is a problem with a mirror, yum eventually outputs a
> line identifying the mirror - nothing like that occurred here. [I suppose I
> could have captured whatever packets it tried to send, and tried to figure
> out what it was doing by looking at their content - but that's a *lot* of
> effort.]
I normally get the following:
[root@neo ~]# yum update
Loaded plugins: dellsysidplugin2, fastestmirror, presto, refresh-packagekit
Determining fastest mirrors
fedora/metalink
| 28 kB 00:00
fedora-debuginfo/metalink
| 21 kB 00:00
updates/metalink
| 14 kB 00:00
updates-debuginfo/metalink
| 8.1 kB 00:00
updates-testing/metalink
| 7.9 kB 00:00
updates-testing-debuginfo/metalink
| 6.6 kB 00:00
* fedora: mirror.sov.uk.goscomb.net
* fedora-debuginfo: mirror.sov.uk.goscomb.net
* rpmfusion-free: download1.rpmfusion.org
* rpmfusion-free-updates: download1.rpmfusion.org
* rpmfusion-free-updates-testing: download1.rpmfusion.org
* updates: mirror.sov.uk.goscomb.net
* updates-debuginfo: mirror.sov.uk.goscomb.net
* updates-testing: mirror.sov.uk.goscomb.net
* updates-testing-debuginfo: mirror.sov.uk.goscomb.net
But that might be from the fastest mirror's plugin I use. 'yum install
yum-plugin-fastestmirror' -> I highly recommend it.
> [ I looked in /etc/yum.repos.d/ - but the entries there specify values such
> as $releasever - so I don't even know which *list* of mirrors it was trying
> to use (typing 'echo $releasever' showed me blanks). And looking at
> https://mirrors.fedoraproject.org with a browser showed me human-readable
> lists rather than what I imagined yum would be using. ]
$releasever is the Fedora release and its a variable inside rpm/yum so
you'll never get anything from the command line.
The bit your interested in is:
#baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-$releas...
The baseurl option (commented out in a default install) only
references a single site ever (not recommended) the mirrorlist option
tells yum to retrieve a list of mirrors from the URL.
>> Generally there's no issues with the Fedora 12 repos at the moment.
>
> Again, I don't know if there is an issue at the Fedora end (i.e., "what is
> there"), or in how my end is asking (this was with build soas-2-beta) - but
> many many of the things I try to fetch with yum on F12-on-XO1 tell me "no
> package xxx available - nothing to do". With F11-on-XO1, such packages
> (vsftpd) *are* in the Fedora repos.
I have no idea how the repos in SoaS-2 are configured but there is no
problem with Fedora repo's at the moment. SoaS-2 should be just using
default Fedora repos.
Peter
14 years, 8 months
New F11 for XO-1.5 build 29
by Chris Ball
http://wiki.laptop.org/go/F11_for_1.5
http://dev.laptop.org/~cjb/f11-1.5/os29
Compressed image size: 379.72mb (+4.06mb since build 28)
Description of changes in this build:
* Switch to ext4 for the root filesystem.
We don't know if our SD will handle an ext4 journal without damaging itself,
but we suspect it might, and it's a good time to find out.
Package changes since build 28:
-alsa-lib-1.0.20-1.fc11.i586
+alsa-lib-1.0.21-1.fc11.i586
-alsa-utils-1.0.20-3.fc11.i586
+alsa-utils-1.0.21-1.fc11.i586
+csound-5.10.1-12.fc11.i586
-csound-5.10.1-9.fc11.i586
-etoys-4.0.2247-1.fc11.noarch
+etoys-4.0.2258-1.fc11.noarch
-gtk2-2.16.6-1.fc11.i586
+gtk2-2.16.6-2.fc11.i586
-kernel-2.6.30_xo1.5-20090827.1247.1.olpc.9e5aad8.i586
+kernel-2.6.30_xo1.5-20090908.1416.1.olpc.d1b0c02.i586
-kernel-firmware-2.6.30_xo1.5-20090827.1247.1.olpc.9e5aad8.i586
+kernel-firmware-2.6.30_xo1.5-20090908.1416.1.olpc.d1b0c02.i586
-libXext-1.0.99.1-2.fc11.i586
+libXext-1.0.99.1-3.fc11.i586
+libcap-ng-0.6.1-1.fc11.i586
-libpurple-2.6.1-1.fc11.i586
+libpurple-2.6.2-1.fc11.i586
-libsilc-1.1.8-5.fc11.i586
+libsilc-1.1.8-7.fc11.i586
-olpc-bootanim-2.5-1.i586
+olpc-bootanim-2.7-1.fc11.i586
-openldap-2.4.15-3.fc11.i586
+openldap-2.4.15-5.fc11.i586
-pciutils-3.1.3-1.fc11.i586
+pciutils-3.1.4-2.fc11.i586
-pciutils-libs-3.1.3-1.fc11.i586
+pciutils-libs-3.1.4-2.fc11.i586
-pulseaudio-libs-0.9.15-14.fc11.i586
+pulseaudio-libs-0.9.15-17.fc11.i586
-pulseaudio-libs-glib2-0.9.15-14.fc11.i586
+pulseaudio-libs-glib2-0.9.15-17.fc11.i586
-smartmontools-5.38-11.fc11.i586
+smartmontools-5.38-13.fc11.i586
-xapian-bindings-python-1.0.14-1.fc11.i586
+xapian-bindings-python-1.0.15-1.fc11.i586
-xapian-core-libs-1.0.14-2.fc11.i586
+xapian-core-libs-1.0.15-1.fc11.i586
+xorg-x11-server-utils-7.4-7.1.fc11.i586
-xorg-x11-server-utils-7.4-7.fc11.i586
-yum-3.2.23-3.fc11.noarch
+yum-3.2.24-1.fc11.noarch
14 years, 8 months
gcc for f11-xo/os6
by Yioryos Asprobounitis
I tried to install some modules in the f11-xo/os6 kernel in an XO-1. However, after I got the olpc-20090806 kernel-src, kernel-headers, kernel-devel etc I can not install gcc because glibc-headers and glibc-devel require glibc 2.10.1-4 while the installed is 2.10.1-5!
Is that a yum problem or should I be activating some other repos?
Should I just get the rpms and force install or will brake the system?
thx
14 years, 8 months
Re: Next Test Day: Sugar on a Stick [Tomorrow]
by Mikus Grinbergs
Booted an XO-1 into soas-2-beta (from USB stick).
Had the usual "SoaS3" problem making it ready for me (I use
__Terminal__ for most of what I do): Initially, boot got as far as
Home View - but the ring did not include Terminal. When I clicked
on the upper right image to switch to Home List view (where I would
have been able to click on Terminal's icon), Sugar vanished.
Used the text console to modify 'favorite_activities' to put
Terminal into the ring, and tried again. Once I was able to use
Terminal, clicked in Home View on some Activities: Browse
(launched); Speak (launched, no sound); Record (did not launch).
Tried to change the timezone in 'My Settings' - Sugar vanished.
To me, soas-2-beta on the XO-1 seems less stable than earlier SoaS3.
Because I am currently not interested in checking out F12-on-XO1, I
did not do any further testing with soas-2-beta.
mikus
14 years, 8 months
Next Test Day: Sugar on a Stick [Tomorrow]
by Sebastian Dziallas
Greetings,
sorry for the late notice and the cross-post. This test day will focus
on Sugar Labs' Sugar on a Stick, a downstream project based on Fedora.
Sugar on a Stick has launched it's first version codenamed "Strawberry"
successfully in June and has recently announced the beta release of its
next version. It contains basically a slightly modified version of the
Sugar Desktop on a Fedora System, prepared to be deployed on USB keys.
The test cases have been developed with the goal in mind to be of value
for both projects, Sugar Labs and the Fedora Project. The latter one
will especially profit from a better integration of the aforementioned
desktop, as well as the testing of the LiveUSB technology. Additionally,
new features like the rebootless live installer, which has been
discussed before (and been included in Fedora lately) are also ready for
testing.
We invite you to jump in #fedora-test-day tomorrow, September 3, and to
join the fun! More concrete information can be found in the wiki:
https://fedoraproject.org/wiki/Test_Day:2009-09-03_SoaS
Thanks,
--Sebastian
14 years, 8 months
New F11 for XO-1.5 build 27
by Chris Ball
http://wiki.laptop.org/go/F11_for_1.5
http://dev.laptop.org/~cjb/f11-1.5/os27
Compressed image size: 375.71mb (-1.62mb since build 26)
Description of changes in this build:
* New kernel with DCON improvements from Paul Fox
* Add / to automatic fsck list in fstab
Package changes since build 26:
-DeviceKit-power-009-1.fc11.i586
+DeviceKit-power-010-0.3.20090810git.fc11.i586
+atlas-sse-3.8.3-4.fc11.i586
-atlas-sse-3.8.3-7.fc11.i586
-bash-4.0-7.fc11.i586
+bash-4.0-8.fc11.i586
-checkpolicy-2.0.19-2.fc11.i586
-cups-libs-1.4-0.rc1.14.fc11.i586
+cups-libs-1.4-0.rc1.15.fc11.i586
-curl-7.19.4-9.fc11.i586
+curl-7.19.6-1.fc11.i586
+dash-0.5.5.1-2.fc11.i586
-dhclient-4.1.0p1-1.fc11.i586
+dhclient-4.1.0p1-4.fc11.i586
-diffutils-2.8.1-23.fc11.i586
-dracut-0.7-1.fc11.i586
+dracut-0.9-2.fc11.i586
-etoys-4.0.2212-1.fc11.noarch
+etoys-4.0.2247-1.fc11.noarch
-farsight2-0.0.12-1.fc11.i586
+farsight2-0.0.14-1.fc11.i586
-fontconfig-2.6.99.behdad.20090508-1.fc11.i586
+fontconfig-2.7.1-1.fc11.i586
-glib2-2.20.4-1.fc11.i586
+glib2-2.20.5-1.fc11.i586
-glibc-2.10.1-4.i686
+glibc-2.10.1-5.i686
-glibc-common-2.10.1-4.i586
+glibc-common-2.10.1-5.i586
-gnome-power-manager-2.26.4-1.fc11.i586
+gnome-power-manager-2.26.4-3.fc11.i586
-gnome-settings-daemon-2.26.1-8.fc11.i586
+gnome-settings-daemon-2.26.1-9.fc11.i586
-gnutls-2.6.6-1.fc11.i586
+gnutls-2.6.6-2.fc11.i586
-gstreamer-plugins-base-0.10.23-3.fc11.i586
+gstreamer-plugins-base-0.10.24-1.fc11.i586
-gstreamer-python-0.10.15-1.fc11.i586
+gstreamer-python-0.10.16-1.fc11.i586
-gtk2-2.16.5-1.fc11.i586
+gtk2-2.16.6-1.fc11.i586
-gupnp-igd-0.1.1-3.fc11.i586
+gupnp-igd-0.1.3-3.fc11.i586
+gvfs-1.2.3-12.fc11.i586
-gvfs-1.2.3-9.fc11.i586
+gvfs-fuse-1.2.3-12.fc11.i586
-gvfs-fuse-1.2.3-9.fc11.i586
-hal-0.5.12-28.20090226git.fc11.i586
+hal-0.5.12-29.20090226git.fc11.i586
-hal-libs-0.5.12-28.20090226git.fc11.i586
+hal-libs-0.5.12-29.20090226git.fc11.i586
-kernel-2.6.30_xo1.5-20090806.0016.1.olpc.1a4850b.i586
+kernel-2.6.30_xo1.5-20090827.1247.1.olpc.9e5aad8.i586
-kernel-firmware-2.6.30_xo1.5-20090806.0016.1.olpc.1a4850b.i586
+kernel-firmware-2.6.30_xo1.5-20090827.1247.1.olpc.9e5aad8.i586
-libcurl-7.19.4-9.fc11.i586
+libcurl-7.19.6-1.fc11.i586
-libmikmod-3.2.0-4.beta2.fc11.i586
+libmikmod-3.2.0-5.beta2.fc11.i586
-libnice-0.0.6-1.fc11.i586
+libnice-0.0.9-1.fc11.i586
-libpurple-2.5.8-2.fc11.i586
+libpurple-2.6.1-1.fc11.i586
-libselinux-utils-2.0.80-1.fc11.i586
-libsemanage-2.0.31-4.fc11.i586
-libvorbis-1.2.0-7.fc11.i586
+libvorbis-1.2.0-8.fc11.i586
-libxml2-2.7.3-2.fc11.i586
+libxml2-2.7.3-3.fc11.i586
-libxml2-python-2.7.3-2.fc11.i586
+libxml2-python-2.7.3-3.fc11.i586
+lyx-cmex10-fonts-1.6.4-1.fc11.noarch
+lyx-cmmi10-fonts-1.6.4-1.fc11.noarch
+lyx-cmr10-fonts-1.6.4-1.fc11.noarch
+lyx-cmsy10-fonts-1.6.4-1.fc11.noarch
+lyx-esint10-fonts-1.6.4-1.fc11.noarch
+lyx-eufm10-fonts-1.6.4-1.fc11.noarch
+lyx-fonts-common-1.6.4-1.fc11.noarch
+lyx-fonts-compat-1.6.4-1.fc11.noarch
+lyx-msam10-fonts-1.6.4-1.fc11.noarch
+lyx-msbm10-fonts-1.6.4-1.fc11.noarch
+lyx-wasy10-fonts-1.6.4-1.fc11.noarch
-mathml-fonts-1.0-23.fc11.noarch
-net-tools-1.60-92.fc11.i586
+net-tools-1.60-93.fc11.i586
-nscd-2.10.1-4.i586
+nscd-2.10.1-5.i586
-nss-3.12.3.99.3-2.11.3.fc11.i586
+nss-3.12.3.99.3-2.11.4.fc11.i586
-nss-softokn-freebl-3.12.3.99.3-2.11.3.fc11.i586
+nss-softokn-freebl-3.12.3.99.3-2.11.4.fc11.i586
-nss_ldap-264-2.fc11.i586
+nss_ldap-264-6.fc11.i586
-policycoreutils-2.0.62-12.12.fc11.i586
-pygtk2-2.14.1-1.fc11.i586
+pygtk2-2.14.1-2.fc11.i586
-readahead-1.4.9-1.fc11.i586
+readahead-1.5.0-1.fc11.i586
-sos-1.8-11.fc11.noarch
+sos-1.8-14.fc11.noarch
-telepathy-gabble-0.7.26-1.fc11.i586
+telepathy-gabble-0.7.26-2.fc11.i586
-telepathy-haze-0.3.0-1.fc11.i586
+telepathy-haze-0.3.1-1.fc11.i586
-totem-2.26.3-1.fc11.i586
+totem-2.26.3-3.fc11.i586
-totem-gstreamer-2.26.3-1.fc11.i586
+totem-gstreamer-2.26.3-3.fc11.i586
-totem-mozplugin-2.26.3-1.fc11.i586
+totem-mozplugin-2.26.3-3.fc11.i586
-tzdata-2009k-1.fc11.noarch
+tzdata-2009k-2.fc11.noarch
-ustr-1.0.4-8.fc11.i586
-xorg-x11-drv-evdev-2.2.4-1.fc11.i586
+xorg-x11-drv-evdev-2.2.5-1.fc11.i586
-xorg-x11-server-Xorg-1.6.2-3.fc11.i586
+xorg-x11-server-Xorg-1.6.3-4.fc11.i586
-xorg-x11-server-common-1.6.2-3.fc11.i586
+xorg-x11-server-common-1.6.3-4.fc11.i586
-xz-4.999.8-0.7.beta.fc11.i586
+xz-4.999.8-0.8.beta.20090817git.fc11.i586
-xz-libs-4.999.8-0.7.beta.fc11.i586
+xz-libs-4.999.8-0.8.beta.20090817git.fc11.i586
-xz-lzma-compat-4.999.8-0.7.beta.fc11.i586
+xz-lzma-compat-4.999.8-0.8.beta.20090817git.fc11.i586
14 years, 8 months
Re: [Sugar-devel] F11 for XO1 - Fonts
by Daniel Drake
2009/9/1 Art Hunkins <abhunkin(a)uncg.edu>:
> I've developed a way to handle fonts both on the XO-1 and on SoaS that fits
> text nicely, on fixed pages, to all-sized screens.
It seems to me like you have this working on 2 screen sizes, but it
certainly won't apply to them all.
You seem to make assumptions like that if 50 characters at a specific
font size can fit on a screen that is 600 pixels wide, then 100
characters will fit on a screen that is 1200 pixels wide. And that's
not how displays and font sizes work.
The number of lines that can fit on a screen (at a certain font size)
does not depend on the aspect ratio, it depends on the physical size
of the screen.
The correct way to do this is to render the fonts and measure the
resultant number of pixels occupied by them, then dynamically adjust.
You can discover the approximate size of a character of a font (in
pixels) to seed the process. Pango provides you all you need to do
this.
Daniel
14 years, 8 months