Hi Peter et al,
I'm still looking for help resolving the dependencies Chris found when he tried to install Gnome.
The issue and thread are documented in the specifications section here: http://wiki.laptop.org/go/Feature_roadmap/Run_Fedora_applications_on_XO
What do we do next when we get a list of "dependency errors"?
Paul,
I believe that you got XFCE running. Can you add the description of what you did to make that happen to this page? http://wiki.laptop.org/go/Feature_roadmap/Run_Fedora_applications_on_XO
I may have a little time tomorrow to try it out if its not too complicated.
Thanks,
Greg S
Hi Greg,
Sorry for delayed response, I've had little internet connectivity so have only had limited mail access and mostly through a windows box :(
I'm still looking for help resolving the dependencies Chris found when he tried to install Gnome.
The issue and thread are documented in the specifications section here: http://wiki.laptop.org/go/Feature_roadmap/Run_Fedora_applications_on_XO
What do we do next when we get a list of "dependency errors"?
Is this on 8.2.0 or joyride? It looks like 8.2 due to the gnome-python version being olpc3. I suspect some of the errors are due to the custom packages, or possibly due to a repo not being available. You can get some weird errors if there's two package provides split across repos (something like a base gnome-python provided by the olpc3 repo where as the gnome-python-blah which was stripped out of the olpc3 build is then provided by the Fedora 9 repo. Overall it looks like an issue with cyrus-sasl. What does a "yum list cyrus-sasl*" show?
Regards, Peter
Hi Greg,
Sorry for delayed response, I've had little internet connectivity so have only had limited mail access and mostly through a windows box :(
I'm still looking for help resolving the dependencies Chris found when he tried to install Gnome.
The issue and thread are documented in the specifications section here: http://wiki.laptop.org/go/Feature_roadmap/Run_Fedora_applications_on_XO
What do we do next when we get a list of "dependency errors"?
Is this on 8.2.0 or joyride? It looks like 8.2 due to the gnome-python version being olpc3. I suspect some of the errors are due to the custom packages, or possibly due to a repo not being available. You can get some weird errors if there's two package provides split across repos (something like a base gnome-python provided by the olpc3 repo where as the gnome-python-blah which was stripped out of the olpc3 build is then provided by the Fedora 9 repo. Overall it looks like an issue with cyrus-sasl. What does a "yum list cyrus-sasl*" show?
The other thing to check for is that there isn't multiple versions installed (rpm -qa | grep cyrus), I've seen this sometimes with things like glibc and openssl where there's both an i386 and i686 version.
Peter
Hi Peter, thanks for the reply,
Is this on 8.2.0 or joyride? It looks like 8.2 due to the gnome-python version being olpc3.
It's running a joyride F10 build, but looks like you're right about olpc3. Here's the /etc/yum.repos.d/olpc-development.repo shipped in Joyride:
[olpc_development] name=OLPC development repository, based on koji tag dist-olpc3-devel. baseurl=http://xs-dev.laptop.org/~cscott/repos/dist-olpc3-devel/ enabled=1 gpgcheck=0 exclude=kernel
[olpc-joyride] name=OLPC 'Joyride' repository baseurl=http://xs-dev.laptop.org/~cscott/repos/joyride/ enabled=1 gpgcheck=0
I suspect some of the errors are due to the custom packages, or possibly due to a repo not being available. You can get some weird errors if there's two package provides split across repos (something like a base gnome-python provided by the olpc3 repo where as the gnome-python-blah which was stripped out of the olpc3 build is then provided by the Fedora 9 repo. Overall it looks like an issue with cyrus-sasl. What does a "yum list cyrus-sasl*" show?
Excluding Packages from Fedora 10 - i386 Finished Excluding Packages from OLPC development repository, based on koji tag dist-olpc3-devel. Finished Excluding Packages from Fedora 10 - i386 - Updates Finished Installed Packages cyrus-sasl-lib.i386 2.1.22-19.fc10 installed Available Packages cyrus-sasl.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-debuginfo.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-devel.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-gssapi.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-krb4.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-ldap.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-md5.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-ntlm.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-plain.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-sql.i386 2.1.22-15.fc9 olpc_development
Thanks!
- Chris.
Hi Chris,
No probs on the reply.
Hi Peter, thanks for the reply,
Is this on 8.2.0 or joyride? It looks like 8.2 due to the gnome-python version being olpc3.
It's running a joyride F10 build, but looks like you're right about olpc3. Here's the /etc/yum.repos.d/olpc-development.repo shipped in Joyride:
[olpc_development] name=OLPC development repository, based on koji tag dist-olpc3-devel. baseurl=http://xs-dev.laptop.org/~cscott/repos/dist-olpc3-devel/ enabled=1 gpgcheck=0 exclude=kernel
[olpc-joyride] name=OLPC 'Joyride' repository baseurl=http://xs-dev.laptop.org/~cscott/repos/joyride/ enabled=1 gpgcheck=0
I suspect some of the errors are due to the custom packages, or possibly due to a repo not being available. You can get some weird errors if there's two package provides split across repos (something like a base gnome-python provided by the olpc3 repo where as the gnome-python-blah which was stripped out of the olpc3 build is then provided by the Fedora 9 repo. Overall it looks like an issue with cyrus-sasl. What does a "yum list cyrus-sasl*" show?
Excluding Packages from Fedora 10 - i386 Finished Excluding Packages from OLPC development repository, based on koji tag dist-olpc3-devel. Finished Excluding Packages from Fedora 10 - i386 - Updates Finished Installed Packages cyrus-sasl-lib.i386 2.1.22-19.fc10 installed Available Packages cyrus-sasl.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-debuginfo.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-devel.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-gssapi.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-krb4.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-ldap.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-md5.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-ntlm.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-plain.i386 2.1.22-15.fc9 olpc_development cyrus-sasl-sql.i386 2.1.22-15.fc9 olpc_development
I would remove the old fc9 build from the olpc_development repo (or even have one for 8.2.0 and one for 9.1.0 so they don't get mixed up). Surely it should be pulling cyrus-sasl from the Fedora repos anyway?
Peter
Hi Peter,
I would remove the old fc9 build from the olpc_development repo (or even have one for 8.2.0 and one for 9.1.0 so they don't get mixed up). Surely it should be pulling cyrus-sasl from the Fedora repos anyway?
I've just pushed a patch to pilgrim's joyride branch to switch the baseurl that gets written out in /etc/yum.repos.d/olpc-development.repo from http://xs-dev.laptop.org/~cscott/repos/dist-olpc3-devel/ to http://kojipkgs.fedoraproject.org/static-repos/dist-olpc4-build-current/i386...
(olpc3 is our 8.2/F9 repo, and olpc4 is the 9.1/F10 repo, so Joyride should have been switched to write out the olpc4 baseurl when we created the new repo.)
And, after the change, we don't have depsolving problems any more! Here's the list of packages to be downloaded -- the next question is going to be how to avoid many of these dependencies. Perhaps instead of trying the groupinstall, we should be hand-picking a smaller base of GNOME packages from this list?
Dependencies Resolved =============================================================================== Package Arch Version Repository Size =============================================================================== Installing: NetworkManager-gnome i386 1:0.7.0-0.12.svn4326.fc10 olpc_development 355 k alacarte noarch 0.11.6-4.fc10 olpc_development 126 k at-spi i386 1.24.0-5.fc10 olpc_development 241 k bluez-gnome i386 1.8-8.fc10 olpc_development 240 k bug-buddy i386 1:2.24.2-1.fc10 olpc_development 725 k compiz-gnome i386 0.7.8-4.fc10 olpc_development 156 k control-center i386 1:2.24.0.1-9.fc10 olpc_development 2.4 M dasher i386 4.9.0-2.fc10 olpc_development 6.7 M eog i386 2.24.2-1.fc10 olpc_development 1.9 M evince i386 2.24.2-1.fc10 olpc_development 1.2 M evince-djvu i386 2.24.2-1.fc10 olpc_development 26 k evince-dvi i386 2.24.2-1.fc10 olpc_development 77 k file-roller i386 2.24.2-1.fc10 olpc_development 1.3 M gcalctool i386 5.24.2-1.fc10 olpc_development 1.6 M gdm i386 1:2.24.0-12.fc10 olpc_development 1.1 M gdm-user-switch-applet i386 1:2.24.0-12.fc10 olpc_development 90 k gedit i386 1:2.24.2-1.fc10 olpc_development 4.2 M gnome-applets i386 1:2.24.2-2.fc10 olpc_development 6.3 M gnome-audio noarch 2.22.2-2.fc10 olpc_development 1.7 M gnome-backgrounds noarch 2.24.0-2.fc10 olpc_development 9.3 M gnome-bluetooth i386 0.11.0-5.fc10 olpc_development 243 k gnome-media i386 2.24.0.1-2.fc10 olpc_development 1.9 M gnome-panel i386 2.24.2-1.fc10 olpc_development 2.9 M gnome-pilot i386 2.0.16-2.fc9 olpc_development 644 k gnome-power-manager i386 2.24.2-2.fc10 olpc_development 2.6 M gnome-screensaver i386 2.24.1-1.fc10 olpc_development 1.8 M gnome-session i386 2.24.2-1.fc10 olpc_development 596 k gnome-system-monitor i386 2.24.1-1.fc10 olpc_development 1.9 M gnome-terminal i386 2.24.2-2.fc10 olpc_development 1.6 M gnome-user-docs noarch 2.22.1-1.fc9 olpc_development 16 M gnome-user-share i386 0.40-3.fc10 olpc_development 92 k gnome-utils i386 1:2.24.1-1.fc10 olpc_development 5.9 M gok i386 2.24.0-2.fc10 olpc_development 1.4 M gthumb i386 2.10.10-3.fc10 olpc_development 2.6 M gucharmap i386 2.24.2-1.fc10 olpc_development 2.4 M gvfs-archive i386 1.0.3-4.fc10 olpc_development 56 k gvfs-fuse i386 1.0.3-4.fc10 olpc_development 20 k gvfs-gphoto2 i386 1.0.3-4.fc10 olpc_development 85 k gvfs-smb i386 1.0.3-4.fc10 olpc_development 111 k libcanberra-gtk2 i386 0.10-2.fc10 olpc_development 20 k metacity i386 2.24.0-2.fc10 olpc_development 1.5 M mousetweaks i386 2.24.2-1.fc10 olpc_development 613 k nautilus i386 2.24.2-1.fc10 olpc_development 4.4 M nautilus-cd-burner i386 2.24.0-1.fc10 olpc_development 521 k nautilus-sendto i386 1.1.0-1.fc10 olpc_development 122 k orca i386 2.24.2-1.fc10 olpc_development 2.2 M pulseaudio-esound-compat i386 0.9.13-6.fc10 olpc_development 13 k pulseaudio-module-gconf i386 0.9.13-6.fc10 olpc_development 18 k pulseaudio-module-x11 i386 0.9.13-6.fc10 olpc_development 24 k scim-bridge-gtk i386 0.4.15-8.fc10 olpc_development 40 k tomboy i386 0.12.0-5.fc10 olpc_development 4.2 M vino i386 2.24.1-1.fc10 olpc_development 507 k xdg-user-dirs-gtk i386 0.8-2.fc10 olpc_development 41 k yelp i386 2.24.0-4.fc10 olpc_development 915 k zenity i386 2.24.0-2.fc10 olpc_development 2.0 M Installing for dependencies: Canna-libs i386 3.7p3-25.fc10 olpc_development 429 k GConf2 i386 2.24.0-1.fc10 olpc_development 1.7 M GConf2-gtk i386 2.24.0-1.fc10 olpc_development 20 k apr i386 1.3.3-1.fc10 olpc_development 133 k apr-util i386 1.3.4-1.fc10 olpc_development 91 k at-spi-python i386 1.24.0-5.fc10 olpc_development 55 k audiofile i386 1:0.2.6-9.fc10 olpc_development 103 k bluez i386 4.19-1.fc10 olpc_development 434 k bluez-libs i386 4.19-1.fc10 olpc_development 66 k cairomm i386 1.6.2-1.fc10 olpc_development 50 k cdrdao i386 1.2.2-5 olpc_development 444 k compiz i386 0.7.8-4.fc10 olpc_development 424 k compiz-fusion i386 0.7.8-2.fc10 olpc_development 1.5 M compiz-fusion-gnome i386 0.7.8-2.fc10 olpc_development 252 k control-center-filesystem i386 1:2.24.0.1-9.fc10 olpc_development 39 k cyrus-sasl-md5 i386 2.1.22-19.fc10 olpc_development 48 k cyrus-sasl-plain i386 2.1.22-19.fc10 olpc_development 28 k desktop-backgrounds-basic noarch 9.0.0-5 olpc_development 2.6 M docbook-dtds noarch 1.0-41.fc10 olpc_development 821 k dvd+rw-tools i386 7.1-1.fc10 olpc_development 138 k eel2 i386 2.24.1-4.fc10 olpc_development 266 k esound-libs i386 1:0.2.41-1.fc10 olpc_development 77 k evolution-data-server i386 2.24.2-1.fc10 olpc_development 4.0 M exempi i386 2.0.1-1.fc10 olpc_development 297 k fedora-screensaver-theme noarch 1.0.0-3.fc10 olpc_development 9.5 k fedorainfinity-screensaver-theme noarch 1.0.0-1.fc8 olpc_development 83 k festival i386 1.96-6.fc10 olpc_development 1.4 M festival-lib i386 1.96-6.fc10 olpc_development 467 k festival-speechtools-libs i386 1.2.96-6.fc10 olpc_development 1.2 M festvox-slt-arctic-hts i386 0.20061229-6.fc10 olpc_development 1.6 M fuse i386 2.7.4-1.fc10 olpc_development 83 k fuse-libs i386 2.7.4-1.fc10 olpc_development 72 k genisoimage i386 1.1.8-1.fc10 olpc_development 570 k glibmm24 i386 2.18.1-1.fc10 olpc_development 302 k gmime i386 2.2.21-1.fc10 olpc_development 167 k gmime-sharp i386 2.2.21-1.fc10 olpc_development 46 k gnome-bluetooth-libs i386 0.11.0-5.fc10 olpc_development 53 k gnome-desktop i386 2.24.2-1.fc10 olpc_development 1.0 M gnome-desktop-sharp i386 2.24.0-3.fc10 olpc_development 207 k gnome-doc-utils-stylesheets noarch 0.14.0-1.fc10 olpc_development 125 k gnome-keyring-pam i386 2.24.1-1.fc10 olpc_development 24 k gnome-mag i386 0.15.4-1.fc10 olpc_development 179 k gnome-menus i386 2.24.2-1.fc10 olpc_development 220 k gnome-panel-libs i386 2.24.2-1.fc10 olpc_development 60 k gnome-python2-applet i386 2.23.0-1.fc10 olpc_development 15 k gnome-python2-bonobo i386 2.22.3-1.fc10 olpc_development 85 k gnome-python2-desktop i386 2.23.0-1.fc10 olpc_development 51 k gnome-python2-extras i386 2.19.1-25.fc10 olpc_development 51 k gnome-python2-gnome i386 2.22.3-1.fc10 olpc_development 82 k gnome-python2-libegg i386 2.19.1-25.fc10 olpc_development 57 k gnome-session-xsession i386 2.24.2-1.fc10 olpc_development 25 k gnome-settings-daemon i386 2.24.1-3.fc10 olpc_development 448 k gnome-sharp i386 2.24.0-1.fc10 olpc_development 326 k gnome-speech i386 0.4.22-1.fc10 olpc_development 51 k gtk-sharp2 i386 2.12.7-1.fc10.1 olpc_development 831 k gtkhtml3 i386 3.24.2-1.fc10 olpc_development 1.1 M gtkmm24 i386 2.14.3-1.fc10 olpc_development 1.1 M gtkspell i386 2.0.13-1.fc10 olpc_development 34 k gvfs i386 1.0.3-4.fc10 olpc_development 1.1 M gvfs-obexftp i386 1.0.3-4.fc10 olpc_development 60 k httpd i386 2.2.10-2 olpc_development 1.1 M httpd-tools i386 2.2.10-2 olpc_development 68 k kpathsea i386 2007-35.fc10 olpc_development 115 k libXScrnSaver i386 1.1.3-1.fc10 olpc_development 16 k libXevie i386 1.0.2-4.fc10 olpc_development 10 k libarchive i386 2.5.5-2.fc10 olpc_development 102 k libbeagle i386 0.3.5-1.fc9 olpc_development 40 k libbtctl i386 0.10.0-5.fc10 olpc_development 44 k libcanberra i386 0.10-2.fc10 olpc_development 66 k libcdio i386 0.80-5.fc10 olpc_development 275 k libexif i386 0.6.16-1.fc9 olpc_development 235 k libgail-gnome i386 1.20.1-1.fc10 olpc_development 26 k libgdiplus i386 2.0-4.fc10 olpc_development 433 k libgdiplus-devel i386 2.0-4.fc10 olpc_development 8.2 k libgnomekbd i386 2.24.0-1.fc10 olpc_development 167 k libgphoto2 i386 2.4.3-1.fc10 olpc_development 1.3 M libgtop2 i386 2.24.0-2.fc10 olpc_development 119 k libgweather i386 2.24.2-1.fc10 olpc_development 13 M libiptcdata i386 1.0.2-2.fc9 olpc_development 43 k libopenraw i386 0.0.5-1.fc9 olpc_development 127 k libopenraw-gnome i386 0.0.5-1.fc9 olpc_development 6.4 k libpurple i386 2.5.2-6.fc10 olpc_development 7.2 M libsamplerate i386 0.1.4-1.fc10 olpc_development 1.3 M libsigc++20 i386 2.2.2-1.fc9 olpc_development 51 k libsilc i386 1.1.7-2.fc10 olpc_development 442 k libsmbclient i386 3.2.5-0.23.fc10 olpc_development 1.3 M libspectre i386 0.2.1-1.fc10 olpc_development 37 k libtalloc i386 1.2.0-23.fc10 olpc_development 53 k libtdb i386 1.1.1-23.fc10 olpc_development 64 k libtool-ltdl i386 1.5.26-4.fc10 olpc_development 39 k libxklavier i386 3.7-3.fc10 olpc_development 57 k meanwhile i386 1.1.0-0.fc10 olpc_development 109 k mesa-dri-drivers i386 7.2-0.15.fc10 olpc_development 2.0 M mesa-libGL i386 7.2-0.15.fc10 olpc_development 167 k mesa-libGLU i386 7.2-0.15.fc10 olpc_development 198 k mono-addins i386 0.3.1-2.2.fc10 olpc_development 265 k mono-core i386 2.0.1-12.fc10 olpc_development 9.9 M mono-data i386 2.0.1-12.fc10 olpc_development 1.5 M mono-data-sqlite i386 2.0.1-12.fc10 olpc_development 151 k mono-extras i386 2.0.1-12.fc10 olpc_development 255 k mono-web i386 2.0.1-12.fc10 olpc_development 2.9 M mono-winforms i386 2.0.1-12.fc10 olpc_development 2.9 M nautilus-extensions i386 2.24.2-1.fc10 olpc_development 46 k ndesk-dbus i386 0.6.1a-2.fc9 olpc_development 58 k ndesk-dbus-glib i386 0.4.1-3.fc9 olpc_development 9.5 k obex-data-server i386 1:0.4.1-1.fc10 olpc_development 75 k openobex i386 1.4-1.fc10 olpc_development 38 k pangomm i386 2.14.1-1.fc10 olpc_development 69 k pilot-link i386 2:0.12.3-18.fc10 olpc_development 1.0 M plymouth-gdm-hooks i386 0.6.0-0.2008.11.17.3.fc10 olpc_development 16 k plymouth-utils i386 0.6.0-0.2008.11.17.3.fc10 olpc_development 22 k pulseaudio i386 0.9.13-6.fc10 olpc_development 407 k pulseaudio-core-libs i386 0.9.13-6.fc10 olpc_development 208 k pyorbit i386 2.24.0-1.fc10 olpc_development 50 k rarian i386 0.8.1-1.fc10 olpc_development 106 k rarian-compat i386 0.8.1-1.fc10 olpc_development 101 k redhat-menus noarch 10.0.1-1.fc10 olpc_development 222 k samba-common i386 3.2.5-0.23.fc10 olpc_development 11 M samba-winbind i386 3.2.5-0.23.fc10 olpc_development 2.9 M scim-bridge i386 0.4.15-8.fc10 olpc_development 99 k sgml-common noarch 0.6.3-26.fc10 olpc_development 43 k solar-backgrounds noarch 0.92.0-1.fc10 olpc_development 13 M sound-theme-freedesktop noarch 0.2-2.fc10 olpc_development 766 k texlive i386 2007-35.fc10 olpc_development 1.9 M texlive-texmf noarch 2007-26.fc10 olpc_development 3.5 M texlive-texmf-dvips noarch 2007-26.fc10 olpc_development 377 k texlive-texmf-errata noarch 2007-4.fc9 olpc_development 3.5 k texlive-texmf-errata-dvips noarch 2007-4.fc9 olpc_development 3.5 k texlive-texmf-errata-fonts noarch 2007-4.fc9 olpc_development 3.6 k texlive-texmf-fonts noarch 2007-26.fc10 olpc_development 56 M unique i386 1.0.0-1.fc10 olpc_development 33 k usermode i386 1.98.1-1 olpc_development 206 k wodim i386 1.1.8-1.fc10 olpc_development 514 k xdg-user-dirs i386 0.10-1.fc9 olpc_development 39 k
Transaction Summary =============================================================================== Install 189 Package(s) Update 0 Package(s) Remove 0 Package(s)
Total download size: 267 M
Thanks!
- Chris.
Hi Chris,
I would remove the old fc9 build from the olpc_development repo (or even have one for 8.2.0 and one for 9.1.0 so they don't get mixed up). Surely it should be pulling cyrus-sasl from the Fedora repos anyway?
I've just pushed a patch to pilgrim's joyride branch to switch the baseurl that gets written out in /etc/yum.repos.d/olpc-development.repo from http://xs-dev.laptop.org/~cscott/repos/dist-olpc3-devel/ to http://kojipkgs.fedoraproject.org/static-repos/dist-olpc4-build-current/i386...
(olpc3 is our 8.2/F9 repo, and olpc4 is the 9.1/F10 repo, so Joyride should have been switched to write out the olpc4 baseurl when we created the new repo.)
And, after the change, we don't have depsolving problems any more! Here's the list of packages to be downloaded -- the next question is going to be how to avoid many of these dependencies. Perhaps instead of trying the groupinstall, we should be hand-picking a smaller base of GNOME packages from this list?
Well its the list up to the "Installing for dependencies" that is explicitly requested, all the below is pulled in for deps. I'm not sure how pilgrim builds the list but I think if it uses kickstart like the other fedora build systems do you should be able to do a specific "-packagename" and its removed from the list.
A quick look through the list..... if you remove tomboy you should loose all the mono deps, bluez-gnome and gnome-bluetooth should drop out all the bluetooth related stuff, nautilus-cd-burner and nautilus-sendto should drop various other non required deps (various CD burning stuff and pidgin etc), compiz* won't be required as I doubt the graphics adapter does cool whirly effects,
That should be a start to reduce the dep list quite significantly.
From there if there's extra deps we need to drop from specific
packages as its for a gnome desktop it would be best to file a bug and link it against the tracker bug for OLPC packages in fedora for easy tracking rather than forking.
Cheers, Peter
Hi Chris,
I would remove the old fc9 build from the olpc_development repo (or even have one for 8.2.0 and one for 9.1.0 so they don't get mixed up). Surely it should be pulling cyrus-sasl from the Fedora repos anyway?
I've just pushed a patch to pilgrim's joyride branch to switch the baseurl that gets written out in /etc/yum.repos.d/olpc-development.repo from http://xs-dev.laptop.org/~cscott/repos/dist-olpc3-devel/ to http://kojipkgs.fedoraproject.org/static-repos/dist-olpc4-build-current/i386...
(olpc3 is our 8.2/F9 repo, and olpc4 is the 9.1/F10 repo, so Joyride should have been switched to write out the olpc4 baseurl when we created the new repo.)
And, after the change, we don't have depsolving problems any more! Here's the list of packages to be downloaded -- the next question is going to be how to avoid many of these dependencies. Perhaps instead of trying the groupinstall, we should be hand-picking a smaller base of GNOME packages from this list?
Well its the list up to the "Installing for dependencies" that is explicitly requested, all the below is pulled in for deps. I'm not sure how pilgrim builds the list but I think if it uses kickstart like the other fedora build systems do you should be able to do a specific "-packagename" and its removed from the list.
A quick look through the list..... if you remove tomboy you should loose all the mono deps, bluez-gnome and gnome-bluetooth should drop out all the bluetooth related stuff, nautilus-cd-burner and nautilus-sendto should drop various other non required deps (various CD burning stuff and pidgin etc), compiz* won't be required as I doubt the graphics adapter does cool whirly effects,
How did you go with this? Did you have any luck? I also realised that if you drop gnome-user-share you'll drop all the httpd requirements.
I was going through the list of stuff at http://wiki.laptop.org/go/Feature_roadmap/Run_Fedora_applications_on_XO and have a few comments on the points made. Some might be obvious, some not so much. * Must support camera, microphone, speakers, wifi 802.11 A/B/G, touchpad, Keyboard, USB interfaces, and SD interface. - being based on Fedora all of the above comes as standard. I presume with the wifi bit you mean support of the onboard wifi interface. * Does not need to make it easy to share files between Fedora and Sugar. - assuming its all running from the same base OS and just switching GUIs this should be OK except for stuff stored in the journal possibly. If its stored in the journal would it be possible to write a gio interface for the journal ? * Must fully support Yum. - This would come as standard. * Must come with nnnn applications on default install (will be chosen and will be a very minimal set). - this would be dependant on the choice of apps. we already have the base of quite a few installed from the gnome side of things (totem, abiword etc) in some cases its a matter of just adding the standard 'GUI' along with the sugar one. * Must boot as fast as Sugar. - in most cases its the other parts of the OS that take the time. Not sure how you'll switch between the two but in the case of a gnome gui it would be mostly the 'login time' difference. * Must support upgrading the Fedora version and the Sugar version in 9.2.0 and future releases. - Like yum support this would be automatic :-) * Must not keep two copies of any files or libraries. Any file which is exactly the same on both Sugar and Fedora images should be used by both and should not take twice the space. - The issue here would be forked libraries. The ones that come to mind specifically are abiword, totem, totem-pl-parser, telepathy and GConf2-dbus. In some cases where the gnome desktop requires evolution-data-server in other areas anyway there is suddenly very little need to keep the forked packages around.
A gnome based desktop make some sense in the discussions as we already package so much of it already
Cheers, Peter
Hi Peter,
How did you go with this? Did you have any luck? I also realised that if you drop gnome-user-share you'll drop all the httpd requirements.
Yep, it worked! I had RPM conflicts in GConf2 (against GConf2-dbus, both ship the same .mo files) and evince (against sugar-evince, both ship the same evince backend shared libraries). Also, it turns out that evince-dvi is responsible for bringing in texlive, via kpathsea.
Here's the command I'm using now:
-bash-3.2# yum -y install NetworkManager-gnome alacarte at-spi bug-buddy control-center eog file-roller gcalctool gdm gdm-user-switch-applet gedit gnome-applets gnome-audio gnome-backgrounds gnome-media gnome-panel gnome-power-manager gnome-screensaver gnome-session gnome-system-monitor gnome-terminal gnome-user-docs gnome-utils gok gthumb gucharmap gvfs-archive gvfs-fuse gvfs-gphoto2 gvfs-smb libcanberra-gtk2 metacity mousetweaks nautilus orca pulseaudio-esound-compat pulseaudio-module-gconf pulseaudio-module-x11 scim-bridge-gtk xdg-user-dirs-gtk yelp zenity
Total size: 152 M
After that completes, you can put "exec gnome-session" in ~/.xsession and restart X to land in a very normal looking F10 GNOME desktop. (I haven't tried to do much with it yet. Sound works, at least.)
Thanks!
- Chris.
chris wrote:
Hi Peter,
How did you go with this? Did you have any luck? I also realised that if you drop gnome-user-share you'll drop all the httpd requirements.
Yep, it worked! I had RPM conflicts in GConf2 (against GConf2-dbus, both ship the same .mo files) and evince (against sugar-evince, both ship the same evince backend shared libraries). Also, it turns out that evince-dvi is responsible for bringing in texlive, via kpathsea.
Here's the command I'm using now:
-bash-3.2# yum -y install NetworkManager-gnome alacarte at-spi bug-buddy control-center eog file-roller gcalctool gdm gdm-user-switch-applet gedit gnome-applets gnome-audio gnome-backgrounds gnome-media gnome-panel gnome-power-manager gnome-screensaver gnome-session
what happens when you push the power button?
i assume the laptop will suspend due to ohmd, but i think g-p-m is doing the same dbus listen, no?
paul =--------------------- paul fox, pgf@laptop.org give one laptop, get one laptop --- http://www.laptop.com/xo
Hi,
what happens when you push the power button?
i assume the laptop will suspend due to ohmd, but i think g-p-m is doing the same dbus listen, no?
We can just set "When power button is pressed: Do nothing" in the g-p-m prefs. Yeah, ohmd is running/working.
- Chris.
chris wrote:
Hi,
what happens when you push the power button?
i assume the laptop will suspend due to ohmd, but i think g-p-m is doing the same dbus listen, no?
We can just set "When power button is pressed: Do nothing" in the g-p-m prefs. Yeah, ohmd is running/working.
i was actually thinking in the other direction: if the ohmd action were disabled, i assume we'd get the g-p-m screen. is that screen tuneable? if g-p-m is possibly going in anyway, it might obviate the power button menu work.
paul =--------------------- paul fox, pgf@laptop.org
Hi Paul,
i was actually thinking in the other direction: if the ohmd action were disabled, i assume we'd get the g-p-m screen. is that screen tuneable? if g-p-m is possibly going in anyway, it might obviate the power button menu work.
I'm not seeing a menu, even after killing ohmd, with "When the power button is pressed: Ask me" chosen in the g-p-m prefs. Dunno why yet.
- Chris.
Hi Chris,
How did you go with this? Did you have any luck? I also realised that if you drop gnome-user-share you'll drop all the httpd requirements.
Yep, it worked! I had RPM conflicts in GConf2 (against GConf2-dbus, both ship the same .mo files) and evince (against sugar-evince, both ship the same evince backend shared libraries). Also, it turns out that evince-dvi is responsible for bringing in texlive, via kpathsea.
Good news. I'm aware of the conflicts you mention. I'm not sure that we need evince-dvi (not sure if its a requirement of anything though and hence gets pulled in automatically). For the evince vs sugar-evince I suspect we need to try and get the mainline evince split out into evince and evince-libs so that we can build sugar-evince against it similar to what we do with abiword and write (I think that's its name). As for the gconf2-dbus...... I know that's used over the usual dbus to drop out the bonobo dependencies but whether that is still a factor at the moment with the other things that pull bonobo in I'm not sure so it might be worthwhile working out whether we stick with it or move back to the mainline version. Not sure who knows the answer to that one, I know DSD got it compiled up but other than that I don't know the best person to ask.
Peter
Hi Peter,
Good news. I'm aware of the conflicts you mention. I'm not sure that we need evince-dvi (not sure if its a requirement of anything though and hence gets pulled in automatically).
That's right, we don't need it. It's part of the groupinstall, but it's not depended on otherwise (and was split out so that people could choose to omit it).
For the evince vs sugar-evince I suspect we need to try and get the mainline evince split out into evince and evince-libs so that we can build sugar-evince against it similar to what we do with abiword and write (I think that's its name).
Yep, sounds good.
As for the gconf2-dbus...... I know that's used over the usual dbus to drop out the bonobo dependencies but whether that is still a factor at the moment with the other things that pull bonobo in I'm not sure so it might be worthwhile working out whether we stick with it or move back to the mainline version. Not sure who knows the answer to that one, I know DSD got it compiled up but other than that I don't know the best person to ask.
I think the reason we're using GConf2-dbus is actually that plain GConf2 didn't work with Rainbow's preforking code after the move to F10, but we've reverted that preforking code for the moment, so perhaps we could just use plain GConf2..
Thanks!
- Chris.
Hi Chris,
For the evince vs sugar-evince I suspect we need to try and get the mainline evince split out into evince and evince-libs so that we can build sugar-evince against it similar to what we do with abiword and write (I think that's its name).
Yep, sounds good.
When I get a sec I'll look at what's required and file a RH bug for evince to see if we can't get the package split up.
As for the gconf2-dbus...... I know that's used over the usual dbus to drop out the bonobo dependencies but whether that is still a factor at the moment with the other things that pull bonobo in I'm not sure so it might be worthwhile working out whether we stick with it or move back to the mainline version. Not sure who knows the answer to that one, I know DSD got it compiled up but other than that I don't know the best person to ask.
I think the reason we're using GConf2-dbus is actually that plain GConf2 didn't work with Rainbow's preforking code after the move to F10, but we've reverted that preforking code for the moment, so perhaps we could just use plain GConf2..
If we can get a definite confirmation of that I'll untag the GConf2-dbus build so that the original GConf gets pulled into joyride and see where we end up from there.
Peter
For the evince vs sugar-evince I suspect we need to try and get the mainline evince split out into evince and evince-libs so that we can build sugar-evince against it similar to what we do with abiword and write (I think that's its name).
Yep, sounds good.
When I get a sec I'll look at what's required and file a RH bug for evince to see if we can't get the package split up.
BTW where does the current sugar-evince srpm live?
Peter
On Fri, Jan 9, 2009 at 5:08 AM, Peter Robinson pbrobinson@gmail.com wrote:
For the evince vs sugar-evince I suspect we need to try and get the mainline evince split out into evince and evince-libs so that we can build sugar-evince against it similar to what we do with abiword and write (I think that's its name).
Yep, sounds good.
When I get a sec I'll look at what's required and file a RH bug for evince to see if we can't get the package split up.
BTW where does the current sugar-evince srpm live?
In koji.
Here is the diff against the corresponding evince version: http://dev.laptop.org/git?p=users/dsd/sugar-evince;a=commitdiff;h=d9b354a931... There are some changes to the core evince source which means that it will be more than just splitting up the F10 evince package. But that will certainly be a step in the right direction.
Daniel
Peter Robinson wrote:
Hi Chris,
I would remove the old fc9 build from the olpc_development repo (or even have one for 8.2.0 and one for 9.1.0 so they don't get mixed up). Surely it should be pulling cyrus-sasl from the Fedora repos anyway?
I've just pushed a patch to pilgrim's joyride branch to switch the baseurl that gets written out in /etc/yum.repos.d/olpc-development.repo from http://xs-dev.laptop.org/~cscott/repos/dist-olpc3-devel/ to http://kojipkgs.fedoraproject.org/static-repos/dist-olpc4-build-current/i386...
(olpc3 is our 8.2/F9 repo, and olpc4 is the 9.1/F10 repo, so Joyride should have been switched to write out the olpc4 baseurl when we created the new repo.)
And, after the change, we don't have depsolving problems any more! Here's the list of packages to be downloaded -- the next question is going to be how to avoid many of these dependencies. Perhaps instead of trying the groupinstall, we should be hand-picking a smaller base of GNOME packages from this list?
Well its the list up to the "Installing for dependencies" that is explicitly requested, all the below is pulled in for deps. I'm not sure how pilgrim builds the list but I think if it uses kickstart like the other fedora build systems do you should be able to do a specific "-packagename" and its removed from the list.
Does pilgrim (Puritan?) use "kickstart" like files? If so, how? If not, why do we not create builds using what seems to be fedora's standard build system?
On Tue, Jan 06, 2009 at 07:40:07PM -0500, Reuben K. Caron wrote:
Peter Robinson wrote:
Hi Chris,
I would remove the old fc9 build from the olpc_development repo (or even have one for 8.2.0 and one for 9.1.0 so they don't get mixed up). Surely it should be pulling cyrus-sasl from the Fedora repos anyway?
I've just pushed a patch to pilgrim's joyride branch to switch the baseurl that gets written out in /etc/yum.repos.d/olpc-development.repo from http://xs-dev.laptop.org/~cscott/repos/dist-olpc3-devel/ to http://kojipkgs.fedoraproject.org/static-repos/dist-olpc4-build-current/i386...
(olpc3 is our 8.2/F9 repo, and olpc4 is the 9.1/F10 repo, so Joyride should have been switched to write out the olpc4 baseurl when we created the new repo.)
And, after the change, we don't have depsolving problems any more! Here's the list of packages to be downloaded -- the next question is going to be how to avoid many of these dependencies. Perhaps instead of trying the groupinstall, we should be hand-picking a smaller base of GNOME packages from this list?
Well its the list up to the "Installing for dependencies" that is explicitly requested, all the below is pulled in for deps. I'm not sure how pilgrim builds the list but I think if it uses kickstart like the other fedora build systems do you should be able to do a specific "-packagename" and its removed from the list.
Does pilgrim (Puritan?) use "kickstart" like files?
Nope.
If not, why do we not create builds using what seems to be fedora's standard build system?
The short answer is that there has never been consensus among the people dealing with OLPC's builds that anaconda was the right tool for the job.
The longer answer involves a lot of politics which I'm /really/ not interested in stirring up but which are unavoidable if you want to really understand how things came to be the way that they are. In order to navigate this quandary, I'm going to offer you a series of thought-questions which, I hope, will lead you to your own answer to your question.
(If you want, you can ask me tomorrow for my answers to them but you should try to construct your own answers first.)
Hope this helps,
Michael
---------
a) Requirements.
1. What do you think a build system for OLPC and for XOs needs to do?
2. What explorations have been made in the area of XO-related build systems?
3. What lists of requirements (or audiences) do each of these explorations seem to be trying to satisfy?
b) History & Incumbency of Pilgrim.
1. Why did davidz write pilgrim?
2. Why did pilgrim not use anaconda?
3. Why did davidz later write livecd-tools using anaconda?
4. What do you have to do in order to get OLPC to use a different build system?
c) People & Politics
1. Who has worked on build-system stuff for XOs? for OLPC?
2. How might we describe their knowledge, skills, interests, aims, etc at the time?
3. What demands were placed on them at the time they worked on build-system related things?
4. How should we describe their relationships with one another?
Does pilgrim (Puritan?) use "kickstart" like files?
Nope.
If not, why do we not create builds using what seems to be fedora's standard build system?
The short answer is that there has never been consensus among the people dealing with OLPC's builds that anaconda was the right tool for the job.
I think also that alot of the automated tools that are now used to build the various Fedora stuff (mock / koji / livecd-tools / appliance-tools) wouldn't have been around when OLPC was first looking for a build system
The longer answer involves a lot of politics which I'm /really/ not interested in stirring up but which are unavoidable if you want to really understand how things came to be the way that they are. In order to navigate this quandary, I'm going to offer you a series of thought-questions which, I hope, will lead you to your own answer to your question.
No argument there.
(If you want, you can ask me tomorrow for my answers to them but you should try to construct your own answers first.)
Hope this helps,
Michael
a) Requirements.
- What do you think a build system for OLPC and for XOs needs to do?
Simplistically build a working bootable OLPC system, but to do that it is required to deal with the boot system, filesystems, storage, security, signing etc of all of the above.
- What explorations have been made in the area of XO-related build systems?
I think the major differences between a standard Fedora system and an OLPC system WRT a build system is the underlying stuff like the boot (lack of BIOS, security etc), the filesystems used, and OLPC security related stuff.
- What lists of requirements (or audiences) do each of these explorations seem to be trying to satisfy?
a lot of them, and a mostly moving target as the project matures and so do the tools around it.
b) History & Incumbency of Pilgrim.
- Why did davidz write pilgrim?
At a guess because the likes of livecd-tools and appliance-tools either didn't exist or were mature enough to meet the needs of OLPC at the time they were required.
- Why did pilgrim not use anaconda?
Didn't meet the current requirements of OLPC at the time. Probably a number of other reasons to do with politics and various other related issues with the size/complexity of it because it handles everything from a server to a netbook running on a platform of i386 right through PPC and IA-64 from a small amount of RAM to terabytes and everything else most of which isn't an issue to OLPC which runs on essentially a single piece of hardware.
Why did davidz later write livecd-tools using anaconda?
What do you have to do in order to get OLPC to use a different build system?
A lot of work and testing for regressions.
c) People & Politics
Not even going to try to answer these ones but no doubt they change with time and what is relevant now has probably changed someone since the beginning.
Peter
-
Chris Ball -
Daniel Drake -
Greg Smith -
John Gilmore -
Michael Stone -
Paul Fox -
Peter Robinson -
Reuben K. Caron