Re: XO Fedora 22 Beta work
On Saturday, April 25, 2015 10:36:49 PM Peter Robinson wrote: On Sat, Apr 25, 2015 at 5:10 AM, Samuel Greenfeld sam...@greenfeld.org wrote: At James' suggestion I looked a bit into a Fedora 22 beta build. I have found the following problems so far getting the RPM dependencies worked out: olpc-library needs to depend on python-jinja2, not python-jinja. The olpc-library RPM also was removed from Fedora, perhaps due to lack of changes abandonment. Likely, I didn't even know it existed. totem-mozplugin no longer exists and was intentionally removed. Given Firefox supports various media codecs internally this might not be a problem for it (apart for vmeta?); but I don't know what webkit-based Browse uses for media players. Gstreamer based as well so I don't see any major issue there except if vmeta doesn't support gstreamer 1.0 xorg-x11-drv-keyboard and -mouse have been replaced by xorg-x11-drv-libinput. See https://fedoraproject.org/wiki/Changes/LibinputForXorg Works fine on SoaS, although I think there might be a need to migrate Control Panel bits, I did send an email about it some time ago to devel@ 14.1.0 has custom F20 systemd binaries, but I am having trouble finding information as to why. If they have relevant changes they need to be ported to F22 if not already present because using the F20 systemd binaries breaks all sorts of library dependencies. The reason is due to changes in firmware loading changes in the kernel and the fact the XO kernels haven't been rebased to something more modern than 3.0+ Patches have been written for the first three that I could submit. We need to come up with a clear direction as to what volunteers and/or OLPC want would actually use for updated XO builds. I only have the time to focus on one set of images. I can help on anything needed that's in Fedora in terms of adding patches there so you don't need to fork but similarly I don't have much time. with Fedora.NEXT we may be able to look at making OLPC builds be an official part of Fedora, tirckiest bit I think would be the kernel. Long term I think it would be good for both OLPC and Fedora for this to happen. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 release candidate 3 (build 22) released
On Fri, 4 Jan 2013 17:08:57 -0300 Manuel Quiñones ma...@laptop.org wrote: Hi, os22, XO-4: I can't install via yum. Happened in os21 and now in os22 too. Gonzalo said to me that this problem doesn't occur in his machine. I am connected to the Internet. $ sudo yum install git Error: cannot retrive metalink for repository: fedora/18/armfp. Please verify its path and try again Make sure that the date and time on your system are correct, you will get this if https things the cert is not valid, which can happen when your time is too far out Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Fedora 18 features that could effect xo-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, there are two features that work together for Fedora 18 The first aims to reduce the size of debuginfo data on disk https://fedoraproject.org/wiki/Features/DwarfCompressor the second intends to include a minimal amout of debuginfo by default http://fedoraproject.org/wiki/Features/MiniDebugInfo the result is that images will likely be slightly larger. Its not known how much bigger it would be it seems like it would be somewhat minimal. Id like for some feedback from the OLPC side of the fence. biggest impact would be on the XO-1 where storage is smallest. Dennis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk/iTx4ACgkQkSxm47BaWfeyQQCfTFivVO4KM9zGmsOA4fgXxRlW sOkAnjE6BODTVAH08qSrJyT2cyTQg9y/ =f7lf -END PGP SIGNATURE- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: The Fedora Fifteen Franken ARM hardfp build 1 for XO 1.75
El Sat, 07 Jan 2012 21:24:29 + Niels de Vos ni...@nixpanic.net escribió: Unfortunately the fedora.repo and fedora-updates.repo are non-functional for Fedora 15 on ARM. Instead, I am now using the most current builds directly from a repository on the koji infrastructure: - http://arm.koji.fedoraproject.org/repos/dist-f15-build/latest/armhfp/ Does it make sense to create tickets for these kind of issues? Or is this email sufficient to help others? MAke sure that time on your system is close to correct. mirrormanager uses https by default. if your time is way off the ssl cert wont check out and things wont work. the repos really do work just fine Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2605
On Wednesday 24 December 2008 02:48:33 am Peter Robinson wrote: +sugar-base 0.83.2-2.olpc4 Good to see this up-leveled -- the previous version of this package as distributed in Joyride was more than a month old. However, that still leaves several packages which appear to be more recent in 'olpc3' than in 'olpc4'. Output of 'yum check-update' : | pyabiword.i386 0.6.1-4.olpc3 | python-telepathy.noarch 0.15.3-1.olpc3 | sugar-journal.noarch 100-1.olpc3 | xorg-x11-drv-evdev.i386 2.0.8-1.fc9 I can comment on a couple of these, but I'm not sure how to fix them: * pyabiword is newer in olpc3 than fc10, but the spec files are basically the same - the olpc3 one seems to have had a no-change rebuild which bumped the version number higher than the fc10 version. There's no olpc4 version as we do not need to fork from the F-10 version - so we should get the fc10 version into joyride. * python-telepathy has the same version 0.15.3-1 in fc10 and olpc3. We should also be using the fc10 version here as we have rebased on F-10 and olpc3 was built on F-9. There's no need for an olpc4 fork of the package as we are using the same version as Fedora. * sugar-journal is no longer a separate package in Sugar 0.83, so there should not be a sugar-journal included in Joyride at all. The sugar package includes the journal functionality now. Basically I think these just need to be untagged in koji. I can look at doing these in a couple of days when I get a proper internet connection back. it needs to be blocked in koji, and pilgrim needs to be told not to include it. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Building Custom Kernel RPMS
On Friday 19 December 2008 01:57:04 pm Erik Garrison wrote: On Fri, Dec 19, 2008 at 07:32:35PM +, Deepak Saxena wrote: Note that this still requires a Fedora/RHEL system to build kernels, or a functioning mock/chroot setup (untested so far). I have tested on F10 and FC6 systems. Please let me know if you have any problems on other systems. What dependencies would prevent this build process from working on any linux system? should work just fine on any system with mock by building in a chroot. building natively would fail due to missing BuildRequires on a non Fedora based system. different vendors use different naming guidelines for packages. if you satisfy the dependencies you could do --nodeps and build. rpm macros would probably be off. cleanest and safest way to build would be always in a mock chroot even on a fedora based system. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: joyride build fixes cont
On Wednesday 19 November 2008 05:50:29 am Peter Robinson wrote: Hi All, Looking further at the issues with joyride in particular the following 3 packages: ntpdate olpcsound olpc-logos Looking at the output of the pilgrim build logs [1] I see the following errors: Setting up Install Process Parsing package install arguments No package olpc-logos available. No package olpcsound available. No package ntp-ntpdate available. Resolving Dependencies The ntp-ntpdate package is now called just ntpdate. I've tagged the standard F-10 build package for olpc-4 in koji so if someone could update the build script for the new name it should be fixed. please untag it. it will be picked up through regular inheritance. by having it tagged any fedora updates will not get picked up automatically. The olpcsound package is built and tagged so should be pulled in for the next joyride. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2546
On Thursday 13 November 2008 04:20:25 pm Build Announcer v2 wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2546 Changes in build 2546 from build: 2544 This build boots and X starts and you can log in at a console. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2541
On Wednesday 12 November 2008 09:24:23 pm [EMAIL PROTECTED] wrote: On Wed, 12 Nov 2008, Build Announcer v2 wrote: I tried to install this, but after the install it hangs when tring to start init (init: invalid option '--init' try init --help for more information) known the next build will have a fixed upstart. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] updating telepathy in OLPC's F9-based images
On Monday 10 November 2008 04:29:31 am Tomeu Vizoso wrote: Hi all, I'm having some trouble updating the telepathy packages in joyride, which is a prerequisite for updating sugar. My plan was to update the telepathy* packages in F9 to the sources of those packages in F10, but I'm having some trouble in getting commit permissions to do that. Perhaps that's not the best way and we should request OLPC-3 branches instead? Or build packages out of koji until we move joyride to F10? Or perhaps we could update to F10 right away? ;) Just to make sure that everyone is aware. devel has been branched for F-10 now. in your fedora cvs checkouts run cvs up -d and you will pull in a new F-10 branch. devel is now targeted at F-11 Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: wpa supplicant init and logging
On Wed, 15 Oct 2008, Ricardo Carrano wrote: Date: Wed, 15 Oct 2008 21:02:24 -0300 From: Ricardo Carrano [EMAIL PROTECTED] To: tech-team [EMAIL PROTECTED], Devel [EMAIL PROTECTED] Subject: wpa supplicant init and logging Hello all! I need help understanding two things regarding the wpa supplicant on the XO. 1 - The init process: If you boot your XO and check the running wpa processes, here is what you'll see: # ps aux | grep wpa root 1310 0.1 0.7 5444 1848 ?S23:46 0:00 /usr/sbin/wpa_supplicant -g /var/run/wpa_supplicant-global -ddd -t But this is not what I would expect by inspecting /etc/init.d/wpa_supplicant and /etc/sysconfig/wpa_supplicant. Actually, after you do a service wpa_supplicant restart you would get what I would expect. # ps aux | grep wpa root 1502 0.0 0.2 5444 580 ?Ss 23:49 0:00 wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -B -u -f /var/log/wpa_supplicant.log Where is the first coming from? NetworkManager it uses wpa_supplicant for wireless authentication /sbin/chkconfig wpa_supplicant --list should show that wpa_supplicant service is not enabled so there is not a service running twice, or the additional overhead of it. 2 - The logging Even if I enable -ddd on the logging (for instance by adding '-ddd' to OTHER_ARGS in /etc/sysconfig/wpa_supplicant and restart the daemon, I won't get anything interesting on the log (/var/log/wpa_supplicant.log). All I got after interesting associations to wpa aps is the following. its because NetworkManager starts wpa_supplicant and uses its own controls for running wpa_supplicant -- Dennis Gilmore (RHCE) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Gnash mp3 sound: installing gstreamer-plugins-ugly on build 767?
On Fri, 2008-10-10 at 00:31 +0800, Carlos Nazareno wrote: Hey OLPC devel! I was wondering if you guys could help me get gstreamer-plugins-ugly installed. Can you guys walk me through this? (disclaimer - linux noob. just started tinkering w/ ubuntu this year) This is with regards to getting Gnash running with sound on the XO, build 767. To get sound (mp3) running on my Fedora desktop, I just did yum gstreamer-ffmpeg and yum gstreamer-plugins-ugly. Okay, with the XO, first installed the Fedora 9 Livna rpm from rpm.livna.org to get Livna added to my repositories. Then, I did a yum install gstreamer-ffmpeg, like I did on my desktop. Next: because of issues with gstreamer in F-9 and the camera on the XO, gstreamer was reverted to the version that shipped with previous releases. you could manually try install the version from livna for Fedora 7. this is an unintended side effect of reverting parts of the software stack. So how do I install libgstsdp-0.10.so.0 and libgstrtsp-0.10.so.0 on my system in order to be able to install gstreamer-plugins-ugly so I can get sound running with Gnash 0.8.3? Can anyone help me with this (and maybe update the Gnash wiki with this info)? Oh, by the way, the Gnash development team thinks it would be great if OLPC dev could use and test newer Gnash dev builds of 0.8.4 with newer OLPC dev builds. Rob, any chance you guys can hand over a Gnash 0.8.4 build before OLPC finalizes XO build 8.2.0? (Oct. 13 I believe?) Best regards, -Naz ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Outage Notification - 2008-09-13 01:00 UTC
On Wednesday 10 September 2008 12:11:07 pm Dennis Gilmore wrote: There will be an outage starting at Y2008-09-13 01:00 UTC, which will last approximately 1 hour. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2008-09-13 01:00 UTC' Affected Services: Buildsystem Unaffected Services: Websites Database CVS / Source Control DNS Mail Torrent Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/830 Reason for Outage: update koji to 1.2.6. it will enable us to turn garbage collection back on. Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage. This work has been completed, all build services restored. Please report any unusual things that you see. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Outage Notification - 2008-09-13 01:00 UTC
There will be an outage starting at Y2008-09-13 01:00 UTC, which will last approximately 1 hour. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2008-09-13 01:00 UTC' Affected Services: Buildsystem Unaffected Services: Websites Database CVS / Source Control DNS Mail Torrent Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/830 Reason for Outage: update koji to 1.2.6. it will enable us to turn garbage collection back on. Contact Information: Please join #fedora-admin in irc.freenode.net or respond to this email to track the status of this outage. signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Fedora Resources
there is a ticket open for fedora to provide OLPC infrastructure resources. https://fedorahosted.org/fedora-infrastructure/ticket/740 Im needing to know what it is the OLPC would like? Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Fedora User Certificates
For all people using koji. Effective immediately we have replaced the CA that is in use for cvs.fedoraproject.org and koji.fedoraproject.org This effects uploading to lookaside cache and building packages. There are some manual steps that everyone needs to do to be able to use the systems again. they are login to https://admin.fedoraproject.org/accounts/ and click on the Download a client-side certificate link at the bottom of the home page. save the output to ~/.fedora.cert rm ~/.fedora-server-ca.cert ~/.fedora-upload-ca.cert fedora-packager-setup then open your browser got to Edit - Preferences - Advanced - Encryption - View Certificates - Your Certificates Select your existing Certificate and remove it then import the new one from ~/fedora-browser-cert.p12 you will be able to log in to koji * Please note that you can only have one client side certificate at a time. when you download a new one your old one is revoked. Please also only click on the Download a client-side certificate link once as it makes multiple requests and revokes all the transient certs. the CRL is at https://admin.fedoraproject.org/ca/crl.pem Thanks for your understanding and patience. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fedora User Certificates
On Friday 22 August 2008 12:46:04 pm John Gilmore wrote: Effective immediately we have replaced the CA that is in use for cvs.fedoraproject.org and koji.fedoraproject.org This effects uploading to lookaside cache and building packages. How do we know whether the old CA or the new CA is the secure one? This email from Dennis could easily be a spoof or a phish: There are some manual steps that everyone needs to do to be able to use the systems again. We've had a problem and we have to re-validate your account. they are login to https://admin.fedoraproject.org/accounts/ and click on the Download a client-side certificate link at the bottom of the home page. save the output to ~/.fedora.cert First give us your username and password. We promise not to abuse it unduly. I specifically did not post a link to the cert download site because I don't want to Then overwrite the securely signed key that has validated the real web site for years -- with whatever we send you from our spoof site. Then you'll REALLY be secure. The OLD CA was destroyed it no longer exists. because we were not issuing certificates correctly and were unable to revoke them. I'm serious. Whether or not there's been a security compromise on the Fedora servers, it would be easy for the people who did it to pull a DNS spoof, get a bunch more passwords, and get many community members to believe that the spoof site is the real thing. I only recommend replacing your Fedora certificate if you have been asked to do so personally, e.g. by phone from a voice that you recognize as a friend or colleague in Fedora. I don't personally know each and every fedora contributor. but if anyone wants me to call them to verify that they need new certs I am more than willing to call each and every person. However if you don't replace the certs you will not have access to cvs or the buildsystem. they are using only the new certs and checking the crl. you can verify the new cert and host key hashes at https://admin.fedoraproject.org/fingerprints of course you have to trust that that is valid and that the whole fedora infrastructure has not been spoofed. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fedora User Certificates
Sending again i forgot to sign the first reply On Friday 22 August 2008 12:46:04 pm John Gilmore wrote: Effective immediately we have replaced the CA that is in use for cvs.fedoraproject.org and koji.fedoraproject.org This effects uploading to lookaside cache and building packages. How do we know whether the old CA or the new CA is the secure one? This email from Dennis could easily be a spoof or a phish: There are some manual steps that everyone needs to do to be able to use the systems again. We've had a problem and we have to re-validate your account. they are login to https://admin.fedoraproject.org/accounts/ and click on the Download a client-side certificate link at the bottom of the home page. save the output to ~/.fedora.cert First give us your username and password. We promise not to abuse it unduly. I specifically did not post a link to the cert download site because I don't want to Then overwrite the securely signed key that has validated the real web site for years -- with whatever we send you from our spoof site. Then you'll REALLY be secure. The OLD CA was destroyed it no longer exists. because we were not issuing certificates correctly and were unable to revoke them. I'm serious. Whether or not there's been a security compromise on the Fedora servers, it would be easy for the people who did it to pull a DNS spoof, get a bunch more passwords, and get many community members to believe that the spoof site is the real thing. I only recommend replacing your Fedora certificate if you have been asked to do so personally, e.g. by phone from a voice that you recognize as a friend or colleague in Fedora. I don't personally know each and every fedora contributor. but if anyone wants me to call them to verify that they need new certs I am more than willing to call each and every person. However if you don't replace the certs you will not have access to cvs or the buildsystem. they are using only the new certs and checking the crl. you can verify the new cert and host key hashes at https://admin.fedoraproject.org/fingerprints of course you have to trust that that is valid and that the whole fedora infrastructure has not been spoofed. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fedora User Certificates
On Friday 22 August 2008 01:18:44 pm Dennis Gilmore wrote: Sending again i forgot to sign the first reply On Friday 22 August 2008 12:46:04 pm John Gilmore wrote: Effective immediately we have replaced the CA that is in use for cvs.fedoraproject.org and koji.fedoraproject.org This effects uploading to lookaside cache and building packages. How do we know whether the old CA or the new CA is the secure one? This email from Dennis could easily be a spoof or a phish: There are some manual steps that everyone needs to do to be able to use the systems again. We've had a problem and we have to re-validate your account. they are login to https://admin.fedoraproject.org/accounts/ and click on the Download a client-side certificate link at the bottom of the home page. save the output to ~/.fedora.cert First give us your username and password. We promise not to abuse it unduly. I specifically did not post a link to the cert download site because I don't want to ::sigh:: i need to fully read my reply before hitting send. I meant to say that i did not paste a more specifc url because I did not want it to look like a philsing attempt. and I also dont want to get people used to emails of that kind. but i wanted to point them in the general direction of the accounts system. I contemplated just saying go to the Fedora Accounts system and get a new cert. without any other detail. That is what i should have done in hindsight. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fedora User Certificates
On Friday 22 August 2008 04:30:09 pm John Gilmore wrote: Isn't it interesting how we have all this public-key infrastructure to secure all these key projects -- but every few years we throw it all out the window and start over -- based on insecure email messages! However if you don't replace the certs you will not have access to cvs or the buildsystem. they are using only the new certs and checking the crl. This sounds even fishier to me. Let's suppose the servers were broken into and severely compromised. (*) What could the miscreants have done that would invalidate every end-user's existing client certificate? nothing. It has been in the pipeline for a while to be replaced.As it was say you lost your cert. which what we issued was a key and a signed certificate. we had no way to revoke that certificate. we took the downtime to implement the changes as a precautionary measure and to enable things to be easier in the future. in the past we had a user paste his cert and key publicly. we ended up changing his username to ensure no one used the certificate/key to do something bad. this was a big gap in the way things were setup initially. https://www.redhat.com/archives/fedora-infrastructure-list/2008- March/msg00155.html lists the plans to replace it it had been brought up a few times before that also. but that's when we formally started working on getting it replaced. There was no break-in to the clients. Why should the clients need to replace anything? Has the server lost its ability to validate the signature on the client certs? There may be large amounts of hassle coming for every Fedora end-user who wants to be able to download only signed packages (if, out of what they describe as an abundance of caution, Fedora changes the signing key for the whole distro). But why also make unnecessary(**) hassle for every Fedora developer? because of bad design decisions way back when all user certs were issues with a serial of 00. while the changes are slim to remote rather than assume no one has certs with higher serial numbers. we made sure that certificates are accounted for. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2213
On Friday 25 July 2008, Daniel Drake wrote: Bert Freudenberg wrote: Am 25.07.2008 um 17:29 schrieb Build Announcer v2: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2213 -gnome-python2-gnomevfs 2.22.1-5.olpc3 +gnome-python2-gnomevfs 2.22.1-3.olpc3 Was this intentional? Yes, it's the same package, I just moved it from public_rpms into Fedora proper. At the same time I resynced the version numbers to follow on directly from F9 (which is currently at 2). Its too late now. but you should have added a .1 so it would have been gnome-python2-gnomevfs 2.22.1-2.olpc3.1 this way you konw exactly what fedora build its based on -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: yum issue on build 2181
On Tuesday 22 July 2008, riccardo wrote: Hi, when I try to install a package on the xo with yum i get: Error: Cannot retrieve repository metadata(repmod.xml) for repository: olpc_development. Please ... I'm sure it worked yesterday with the same build. Fedora's buildsystem is undergoing maintenance right now and is down. we point directly at it with our yum configs. the maintenance is expected to last another 4 hours or so. The database is being migrated to a new dedicated box. the postgresql dump is 5gb -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: VPN with NetworkManager
On Wednesday 16 July 2008, ffm wrote: Is there support of VPNs in the network manager? (I'm not sure if there is more than one type, but I'm wondering if such support exists at all) NetworkManager supports pptp, openvpn, and vpnc(cisco) but we dont support any of then on the XO. -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Java
On Monday 14 July 2008, David Leeming wrote: Just been browsing the Java pages on the wiki and confirming to myself the Sun Java version installs but the plugin does not load. A pity, as I have installed on a school server an excellent UNESCO CD of educational materials Strengthening ICTs in Schools and Schoolnet Project in the ASEAN Setting which has hundreds of nice educational applets. Seems the last recorded activity on getting Java to work was about 5 months ago... or can anyone update me? David Leeming Solomon Islands I would suggest that you yum install java-1.6.0-openjdk-plugin and try use it instead. Fedora 9 gives us a truely free java its based on openjdk with some bits pulled in from icedtea to replace the non-free bits. it passes the java test suites and is a certified java. -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: User-visible Fedora 9 features
On Monday 14 July 2008, Michael Stone wrote: From my perspective, the user-visible and developer-visible feature is that, with root authority, you can install RECENT software which is available in Fedora. This really matters for G1G1 people and for our ability to attract Fedora contributors. Not so visible is gcc 4.3, glibc 2.8, the ability to have a truely free java, visible Faster X Fedora 9 feature list is at http://fedoraproject.org/wiki/Releases/9/FeatureList the fedora feature proposal process is http://fedoraproject.org/wiki/Features/Policy#feature-proposal tracking of F10 features is http://fedoraproject.org/wiki/Releases/10/FeatureList We should propose features for things we want done and advertised. Sugar as a desktop option should be a feature for F10, there is 2 things we need. sugar to work with NM-0.7 and more activities packaged. this is a good place where we can up the visibility of OLPC and sugar. The OLPC-visible feature is that nobody is going to accept patches to F-7 packages and that nobody is going to be excited about fixing bugs that we uncover in them. Its not that nobody is going to accept patches. they can, but there is no way to build the updates, all the Fedora 7 tags have been disabled. there is no way to build into them. -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New 8.2 Stream
in preparation for 8.2 we have a new 8.2 stream it can be found at http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/ Please test and file bugs against it. This is the stream intended for the 8.2 test builds. -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: koji vs. dropbox
On Monday 07 July 2008, Polychronis Ypodimatopoulos wrote: This is probably meant for the release team. Is the dropbox mechanism for updating rpms in joyride still working? According to http://wiki.laptop.org/go/Build_system the dropbox should work but newer RPMs of cerebro don't get pulled into joyride. Rumors have it that this mechanism no longer works and koji must be used instead. Are there newer instructions on the wiki anywhere? Pol It still works but is strongly discouraged. I would like to see it dropped entirely for the next release. if there not getting picked up it likely means you have not increased the EVR of your package and its not considered the latest. or its in and you just did not realised it because its the same EVR it was not tracked. -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: koji dependency problem building telepathy-gabble
On Friday 04 July 2008, Morgan Collett wrote: Dennis, I couldn't build telepathy-gabble 0.7.6 in OLPC-3 because it depends on telepathy-glib = 0.7.8: http://koji.fedoraproject.org/koji/getfile?taskID=694418name=root.log Guillaume built the latest telepathy-glib in F-9: http://koji.fedoraproject.org/koji/buildinfo?buildID=54696 However I still can't build telepathy-gabble - same problem. Do you need to tag telepathy-glib into dist-olpc3 or something? Yes, its in dist-f9-updates-candidate we only pull in automatically released updates. ive tagged it in for us so you can build against it now. -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Inappropriate use of private meetings lists. (reply to).
On Wednesday 02 July 2008, Jim Gettys wrote: Here's mailman's recommendation about replyto... http://lists.laptop.org/admin/devel/?VARHELP=general/reply_goes_to_list - Jim I personally really dislike being CC'd on lists im subscribed to I find it extremely poor netiquette of all the mailing lists im subscribed to OLPC's are the only ones that dont set replyto the list. It and the huge amount of cross posting on OLPC lists really irritate me. its a very standard convention to keep list mail on lists. if you need to take something off list then you should go through the steps needed to do so. i personally always use the reply to list option my client gives me. When i get CC'd i dont get the mailman email only the cc'd one which goes to different folders where i might not see the mail for awhile. It outright breaks my procmail recipes, because mailman correctly doesnt send me a duplicate email. I filter my list mail based on the X-BeenThere: header -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Inappropriate use of private meetings lists. (reply to).
On Wednesday 02 July 2008, Carol Lerche wrote: I don't understand the argument that forcing Reply-to to be back to the list eradicates a list participant's ability to get the reply on their preferred email address. Presumably they replied to the list via this address. By forcing Reply-to to the list address, all subscribers should receive the reply in the way they specified when they subscribed to it. What am I missing? by setting the replyto the list i wont get ccd on email when people reply to all because that is the easy way to make sure it goes back to the list in the current setup. instead I will get responses via mailmain and not direct and the mail will have the X-BeenThere header and will be filed appropriately on my mail server. mailmans recommendation works if you use the list to start private conversations. but when you want public discussion as we do. you are much better off setting ReplyTo the list. Please someone who is an admin set the replyto the list. 2008/7/2 Dennis Gilmore [EMAIL PROTECTED]: On Wednesday 02 July 2008, Jim Gettys wrote: Here's mailman's recommendation about replyto... http://lists.laptop.org/admin/devel/?VARHELP=general/reply_goes_to_list - Jim I personally really dislike being CC'd on lists im subscribed to I find it extremely poor netiquette of all the mailing lists im subscribed to OLPC's are the only ones that dont set replyto the list. It and the huge amount of cross posting on OLPC lists really irritate me. its a very standard convention to keep list mail on lists. if you need to take something off list then you should go through the steps needed to do so. i personally always use the reply to list option my client gives me. When i get CC'd i dont get the mailman email only the cc'd one which goes to different folders where i might not see the mail for awhile. It outright breaks my procmail recipes, because mailman correctly doesnt send me a duplicate email. I filter my list mail based on the X-BeenThere: header -- Dennis Gilmore ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2097
On Wednesday 02 July 2008, Daniel Drake wrote: On Wed, 2008-07-02 at 03:27 -0700, [EMAIL PROTECTED] wrote: -cdparanoia-libs alpha9.8-30 +cdparanoia-libs 10.0-2.fc9 -mesa-libGL 7.1-0.31.fc9 +mesa-libGL 7.1-0.35.fc9 -mesa-libGLU 7.1-0.31.fc9 +mesa-libGLU 7.1-0.35.fc9 what is bringing in these as dependancies? cdparanoia-libs: totem-gstreamer-2.23.2-4.fc9.i386 gstreamer-plugins-base-0.10.19-2.fc9.i386 gstreamer-python-0.10.11-2.fc9.i386 gstreamer-plugins-good-0.10.8-5.fc9.i386 totem-2.23.2-4.fc9.i386 totem-mozplugin-2.23.2-4.fc9.i386 totem-xine-2.23.2-4.fc9.i386 mesa-libGL: mesa-libGLU-7.1-0.31.fc9.i386 totem-xine-2.23.2-4.fc9.i386 xorg-x11-utils-7.3-3.fc9.i386 xine-lib-1.1.12-2.fc9.i386 mesa-libGLU: xine-lib-1.1.12-2.fc9.i386 totem-xine-2.23.2-4.fc9.i386 I don't think anyone is really arguing that these should be included in OLPC builds, we just need time to make the appropriate modifications so that they get kicked out. You can see a list of new packages here: http://dev.laptop.org/~bert/update.1-joyride.html and here is the tracker bug: http://dev.laptop.org/ticket/7353 I am working on totem so that these extra deps will all fall out. Im doing it in a way that will ease long term maintainence of our totem package. -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Inappropriate use of private meetings lists. (reply to).
On Wednesday 02 July 2008, Bert Freudenberg wrote: Am 02.07.2008 um 19:33 schrieb Dennis Gilmore: by setting the replyto the list i wont get ccd on email when people reply to all because that is the easy way to make sure it goes back to the list in the current setup. instead I will get responses via mailmain and not direct and the mail will have the X-BeenThere header and will be filed appropriately on my mail server. Since you're doing fancy mail filtering on your end anyway, why don't you just discard the duplicate CC based on message ids? See man procmailex for an example using formail -D. because i only get one copy of the email and its not from mailman when im on the CC list -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2094
On Tuesday 01 July 2008, C. Scott Ananian wrote: On Tue, Jul 1, 2008 at 2:31 PM, Build Announcer v2 [EMAIL PROTECTED] wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2094 Changes in build 2094 from build: 2092 Size delta: -0.79M -fonts-thai-ttf 0.4.4-1olpc1.2 Was this intentional? I think Bryan Berry's like to notice this gone... --scott I did not do it. I guess someone cleaned up somebodies public_rpms i was going to ask you if you did it. I did find an upstream for it. we will need to create a new set of rpms. we only ever had a rpm no src.rpm -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [SURVEY] builders, how do you build? what do you build?
On Friday 27 June 2008, Erik Garrison wrote: Developers, specifically those running build systems, Many of us are confused about the software flows inherent in the daily build processes which are occuring at OLPC. I would like to conduct a simple survey of all people building software for OLPC so that all of us can better understand the sources of the software running on the XO and XS without individually hassling the responsible parties every time we have generic questions about their build processes. Builders, please describe your local build network: Going forward we will only accept rpms that are built in koji.fedoraproject.org for inculsion into the images. if you test build you should only build using mock. The attached mock config file will work for the current Fedora 9 based builds. -- Dennis Gilmore config_opts['root'] = 'olpc-3-i386' config_opts['target_arch'] = 'i386' config_opts['chroot_setup_cmd'] = 'groupinstall buildsys-build' config_opts['dist'] = 'olpc3' # only useful for --resultdir variable subst config_opts['yum.conf'] = [main] cachedir=/var/cache/yum debuglevel=1 reposdir=/dev/null logfile=/var/log/yum.log retries=20 obsoletes=1 gpgcheck=0 assumeyes=1 # repos [fedora] name=fedora mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-9arch=i386 failovermethod=priority [updates-released] name=updates mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-f9arch=i386 failovermethod=priority [local] name=local baseurl=http://koji.fedoraproject.org/static-repos/dist-olpc3-build-current/i386/ signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Olpc3 vs Joyride
On Monday 30 June 2008, Jim Gettys wrote: Dennis: OLPC csound is an *exact* formal *subset* of full csound-5 built from the same sources as csound-5. It gets rid of tk/tcl dependency we don't want to carry in csound - Jim There are much better ways to achieve that goal. than what was done. but its too late now. I'm working on defining some macros in totem right now so we can always take the latest fedora spec, change some 0's to 1's and build a much more minimalistic totem that's suitable for us. What is done is done now. On Sun, 2008-06-29 at 17:25 -0500, Dennis Gilmore wrote: On Sunday 29 June 2008, Bert Freudenberg wrote: Am 30.06.2008 um 00:05 schrieb Dennis Gilmore: On Sunday 29 June 2008, Bert Freudenberg wrote: I reanimated my script that shows differences between the latest joyride and candidate builds: http://dev.laptop.org/~bert/olpc3-joyride.html ... and in particular added a section to easily see what packages are in olpc3 and not in joyride, and vice versa. There are not only differences in package versions, but also in which packages are in. I wondered, for example, why csound is missing from joyride ... a second copy of csound landed in fedora as olpcsound. it is built specifically for olpc and is in joyride. If it was named csound-olpc that would have been more obvious ... - Bert - Yes, first i heard of it was when i was asked to switch out csound and csound- python for olpcsound. Had i been asked before hand i could have suggested a way that the csound spec could have produced csound csound-python and csound- olpc. but what is done is done. I personally don't like anything being called olpc-foo, I think we should write code that is useful outside of OLPC, useful to the whole world. In which case the naming is really a poor choice. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: joyride builds
On Sunday 29 June 2008, Tomeu Vizoso wrote: Hi, from joyride 2083, we don't get announcements, and 2084 is the last build offering images and that can be updated with olpc-update. Anybody knows what's going on? somebody removed 2085 and 2086 I restarted the announcer even though it seemed to be running ok. -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Olpc3 vs Joyride
On Sunday 29 June 2008, Bert Freudenberg wrote: I reanimated my script that shows differences between the latest joyride and candidate builds: http://dev.laptop.org/~bert/olpc3-joyride.html ... and in particular added a section to easily see what packages are in olpc3 and not in joyride, and vice versa. There are not only differences in package versions, but also in which packages are in. I wondered, for example, why csound is missing from joyride ... a second copy of csound landed in fedora as olpcsound. it is built specifically for olpc and is in joyride. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Olpc3 vs Joyride
On Sunday 29 June 2008, Bert Freudenberg wrote: Am 30.06.2008 um 00:05 schrieb Dennis Gilmore: On Sunday 29 June 2008, Bert Freudenberg wrote: I reanimated my script that shows differences between the latest joyride and candidate builds: http://dev.laptop.org/~bert/olpc3-joyride.html ... and in particular added a section to easily see what packages are in olpc3 and not in joyride, and vice versa. There are not only differences in package versions, but also in which packages are in. I wondered, for example, why csound is missing from joyride ... a second copy of csound landed in fedora as olpcsound. it is built specifically for olpc and is in joyride. If it was named csound-olpc that would have been more obvious ... - Bert - Yes, first i heard of it was when i was asked to switch out csound and csound- python for olpcsound. Had i been asked before hand i could have suggested a way that the csound spec could have produced csound csound-python and csound- olpc. but what is done is done. I personally don't like anything being called olpc-foo, I think we should write code that is useful outside of OLPC, useful to the whole world. In which case the naming is really a poor choice. -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2072
On Wednesday 25 June 2008, Michael Stone wrote: -rainbow 0.7.13-1.olpc2 +rainbow 0.7.5.11.20080104git6c25f7-1.olpc2 What's with the major rainbow regression? You are probably lucky its even in the build. my guess its in a joyride repo. and has not been built for OLPC-3. -- Dennis Gilmore signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Koji Tags for 8.2.0
On Friday 13 June 2008, C. Scott Ananian wrote: On Fri, Jun 13, 2008 at 12:23 AM, Michael Stone [EMAIL PROTECTED] wrote: Questions? Complaints? Pet peeves? I'd rather rename our build roots to either correspond to fedora releases or to olpc releases. It seems that the 'olpc2, olpc3, ...' numbering is a historical accident only, and just erects another barrier to someone trying to understand how to contribute. A new developer might ask, I want to tag something for the 8.2 release, what branch should I use? and then have to be told the arcane history of olpc buildroots to understand why the answer is olpc3 and not olpc4 (say). Historically, we've shifted build roots only when we've moved from one fedora major release to another. So, olpc-f9, olpc-f10 would be one naming scheme which is slightly easier to explain: you just have to explain that 8.2 is based on fedora 9. If the builds are named after olpc releases (olpc-8.2, etc) they need no explanation, although that means that we create a new build root for (say) olpc-8.3 even if it weren't strictly necessary. (Keeping the olpc-8.2 build root for the 8.3 release would bring us back into confusion-land.) The one complaint I hear over and over again is that our version/build numbering scheme is too complex and baroque. Absent compelling evidence to the contrary, I'd prefer to keep the names as simple as possible, with as few different numbering schemes as possible, and where we must have numbers, as far as possible use already existing numbers (like fedora builds) instead of inventing our own. --scott Scott, I fully agree which is why i said what i said http://lists.laptop.org/pipermail/devel/2008-April/012513.html and http://lists.laptop.org/pipermail/devel/2008-April/012644.html moving forward if we used say olpc-f9 what disttag should we use. if we use .fc9 as fedora uses its harder to easily see what packages we diverge on. i like .olpc3 as its clear that we have diverged on those packages and anything .fc9 comes from fedora. i don't particularly like .olpcf9 but that's certainly an option. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Build streams; preparing for 8.2 release.
On Thursday 12 June 2008, Chris Ball wrote: Hi, At the IRC software meeting yesterday we discussed creating some new build streams in preparation for our August 8.2 release. These streams were proposed: * Unstable/Joyride: This will move immediately (well, within a day or two) to be a copy of the olpc-3 stream, which is a build stream preparing for a switch to Fedora 9, instead of the current Fedora 7. The Joyride release process will continue to be followed here. There is still a lot of work to be done on the F9-based build: it will be broken for a while as the kinks are worked out. Please help! * Testing: This will also be a copy of olpc-3, but with a different release process. Changes will be moved from unstable into testing upon negotiation with the release engineer, Michael Stone. This build stream will be used by our QA team and community to assess the readiness of features for the 8.2 release. * Stable: Stable builds are specified by their release name (e.g. 8.1.1, 8.2), and the procedure for packages moving from Testing into Stable releases involves the Unscheduled Release Process: http://wiki.laptop.org/go/Unscheduled_software_release_process Anyone familiar with Debian's build naming will see intentional similarities here. As i have said previously and repeatedly been ignored (like most of what i say). this process will not work. period. It cant be made to work in the same fashion as Debian because its not Debian. everyone needs to quit trying to fit square pegs into round holes. things more than likely will never be able to move from testing into stable in the proposed format. why? because Testing is based on F-9 and uses the F-9 toolchain and dependencies. and stable is based on F-7 which uses completely different toolchain and dependencies. We need finer grained control over things. We need to follow the fedora process here if we want things to work. Throw away what you know about debian's process. right now it counts for squat. Each stable tree need to have its own updates and updates-testing tree. which means once we create a stable branch we no longer build to it instead we build to a updates-testing-candidate tag we them move a package to updates-testing after testing we move to updates we can then do stable releases based on base + updates So we now have dist-olpc3 its a development tree things are automatically added to that tree as built. when we release a stable build on dist-olpc3 we freeze that tag forever. potential updates will then get build against dist-olpc3 and dist-olpc3-updates. they will land in dist-olpc3-updates-candidate developer will request that they get pushed to dist-olpc3-testing a which point rpms will be signed and pushed to a yum repository where they can be tested. once they have proved themselves in testing. we can then push to dist-olpc3-updates. This means that we will sign all the rpms we push for stable trees. we will need to have a popper master mirror that can be mirrored out. development tree rpms will be unsigned. we can then maintain multiple stable trees. if we need to maintain two stable trees off of one fedora release then we can branch things and have a dist-olpc3-1 for instance I want to reiterate that OLPC needs to work with fedora. We are based on Fedora and continue to cause ourselves unneeded pain by not working with fedora. If someone is looking for a good way to contribute to OLPC then please get involved in packaging for Fedora. we have many things that need to be put into fedora.including olpcrd etoys pyabiword rainbow olpcupdate olpccontents bootanim bootfw fonts-thai-ttf olpc-library-core olpc-library-common olpc-licenses squeak-vm olpc-logos libabiword libabiword-plugins GConf2-dbus hulahop Some of the require other packages not in fedora. some of which olpc has forked. we also need to ensure we do our work upstream. doing things upstream means that 1) We help everybody not just ourselves 2) that the maintainence burden is smaller Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Build streams; preparing for 8.2 release.
On Thursday 12 June 2008, Chris Ball wrote: Hi Dennis, As i have said previously and repeatedly been ignored (like most of what i say). this process will not work. period. It cant be made to work in the same fashion as Debian because its not Debian. everyone needs to quit trying to fit square pegs into round holes. things more than likely will never be able to move from testing into stable in the proposed format. why? because Testing is based on F-9 and uses the F-9 toolchain and dependencies. and stable is based on F-7 which uses completely different toolchain and dependencies. We need finer grained control over things. I think you need to read the proposal again. Unstable and Testing would immediately be based on F9, and there is no stable other than released builds -- stable is what happens to testing when it's done, so there's no mix of F9 and F7 here. An F9 testing build becomes an F9 stable release with its own release name, such as 8.1.1. from your initial email: Stable: Stable builds are specified by their release name (e.g. 8.1.1, 8.2), and the procedure for packages moving from Testing into Stable releases involves the Unscheduled Release Process: http://wiki.laptop.org/go/Unscheduled_software_release_process that indicate you intend to move updates from a F-9 base to a F-7 base. I dont know how else to read it. if im wrong please tell me how i should interpret it. Throw away what you know about debian's process. right now it counts for squat. I don't know what you mean by this. All we're doing is defining three build names, and (our own) processes for moving packages between them. We constantly seem to be having the debian does it this way so lets do it that way discussion. rather than asking how fedora does it. If we find the fedora way to be lacking then we should work to improve that. if it means looking at how Debian does it and saying thats much better then so be it. but lets not make it the first choice. We should work to improve the fedora process for all of fedora's users derivatives. Dennis P.S. please reply to list and not CC me on mail to lists i'm known to be subscribed to. /me would like to see us doing a better job of not cross posting email and not replying to all but just to list. signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Build streams; preparing for 8.2 release.
On Thursday 12 June 2008, Chris Ball wrote: Hi Dennis, from your initial email: Stable: Stable builds are specified by their release name (e.g. 8.1.1, 8.2), and the procedure for packages moving from Testing into Stable releases involves the Unscheduled Release Process: http://wiki.laptop.org/go/Unscheduled_software_release_process that indicate you intend to move updates from a F-9 base to a F-7 base. I dont know how else to read it. if im wrong please tell me how i should interpret it. The interpretation should be that we'll have an F-9 base in testing, and then we'll make a release called, say, 8.2 that contains that build. For the release after that, we'll have an F-10 base in testing, and then we'll make a build called 8.3 that contains that. There is no overlap between the 8.2 stable build and the 8.3 stable build; they're independent. Perhaps you're having trouble because you're imagining stable as existing permanently, rather than once per release. Stable is just a symlink to the latest build that made it out of testing into a named release. There would never be a reason to have stable be a different base to the testing build that it came from. so what happens when we have 2 or stable releases to support. how do i get updates into the older ones? this is the workflow that i am envisioning. We constantly seem to be having the debian does it this way so lets do it that way discussion. rather than asking how fedora does it. I don't think we're borrowing anything from Debian other than the names unstable, testing and stable. We aren't giving them the meanings that Debian assigns to those names. We aren't proposing any modification of our build process, even, except for a separate build that takes changes less regularly than Joyride so that it can have stronger change control. I don't have an issue with the naming. its is the fact that we will have multiple stable releases to support. and I don't see how we can do that with the proposed format. to me and i feel like i'm on the outside here. it looks like we have taken the workflow that debian has and said we will do the same. If we find the fedora way to be lacking then we should work to improve that. if it means looking at how Debian does it and saying thats much better then so be it. but lets not make it the first choice. We should work to improve the fedora process for all of fedora's users derivatives. I don't know of a Fedora way (or a Debian way) for creating a separate build stream for testing at a slower rate than Rawhide; let me know if there is. It sounds like you're chiefly upset that we're using the unstable/testing/stable nomenclature. I don't much care about what we call them; feel free to propose alternate names if it would make you happier. the workflow i'm envisioning releases will be similar to the way that fedora unity releases update respins. in that when we fork from the development tree. we have a series of releases to stabalise the builds. but we will continue development for that branch at a much slower pace. fixing bugs etc. we will then do periodic spins from it. The main difference to what you proposed and what i.m proposing is that we will be supporting multiple stable branches. and some adjustments in workflow to accommodate those changes. We should talk about this tuesday afternoon when im there in person. It will be the only time that i am in the office next week. The rest of my the week ill be doing things for fudcon. I will be in 1cc 23rd-27th Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Build streams; preparing for 8.2 release.
On Thursday 12 June 2008, C. Scott Ananian wrote: Is the piece we're missing the correlation with koji branches / repository names? I've tried to encourage people to think of a more clever naming scheme, but lacking that I suggest that we name our branches according to our stable releases. For example: olpc8.1 - repo for 8.1, 8.1.1, 8.1.2, etc with tags for each release olpc8.2 - repo for 8.2, 8.2.1, 8.2.2, etc with tags for each release So our 'stable' build currently would come from the olpc8.1 branch, testing from olpc8.2, and unstable from olpc8.2 plus an 'unstable' repository or an 'olpc8.2-unstable' tag. When we release 8.2 we start an olpc8.3 or olpc9.1 branch. Do we need the 'dist-' prefix currently used by koji? If so, then add 'dist-' to the tags above. --scott This is fine as long as we know we cannot move from testing to stable when stable is based on 8.1 and testing is based on 8.2 things may be ok but differences in the toolchain could result in everything including the kitchen sync being brought in. that is why i proposed that each stable tree has its own testing branch. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Release Process (Dennis' Take)
I have a few ideas on how we should do this. It is largely influenced by Fedora and as we are based on fedora and we *SHOULD* be working with fedora i think that should weigh heavily in in its favour. Major disruptive development and change happens in a development branch. when it gets closer to basing a release on the development branch things slow down and stabalise. This branch will sometimes not work but that's ok. this is where we can define major goals and do the most disruptive work. i would like to see us have images based on fedora's rawhide. with a weekly image and using yum in the interim to pull in updates we can do alot of new and boundry pushing work. the development tree will get forked off at set times for new stable releases. at this point the new branch will be used for final stabalisation while the devel branch moves forward. once the branch is stable we will re-target builds to an updates testing build target. updates-testing will be tested via yum updates. when deemed stable they will move into updates. we can build images from stable and updates. this will allow us to do bug fix builds as point releases. By using yum we can easily test pending updates. We can then maintain multiple stable trees. For instance OLPC-2 OLPC-3 OLPC-3.1 OLPC-3.2 OLPC-4 OLPC-4.1 To date we have had one major flaw. we have done development and stable releases form the same tree. this causes us issues. Due to the way inheritance works in koji we can do many stable releases based on the same fedora release. The one thing we need to ensure we do is to create a new cvs branch when we do a new stable release. bug fix releases do not need new branches as they come from updates-testing. I would like us to define a set of features for a release but for it to be time based, this gives us goals to work towards. We need to regularly evaluate features and see if we drop them or put more resources on them to ensure that they are completed in time. We need to be very clear in what we aim to achieve and do everything we can to make sure it happens. these features/goals, should be for infrastructure, support, and all the other pieces that make up OLPC. Lastly we should have fun while we do this. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 1970
On Wednesday 21 May 2008, Tomeu Vizoso wrote: On Wed, May 21, 2008 at 9:46 PM, Build Announcer v2 [EMAIL PROTECTED] wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1970 Changes in build 1970 from build: 1949 Size delta: 0.00M ... -sugar 0.79.4-1.olpc2 +sugar 0.75.15-1.olpc2 ... -sugar-toolkit 0.79.6-1.olpc2 Dennis, can you untag sugar 0.75.15? That one was meant for the update.1 builds. already done signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ssh key update IMPORTANT security advisory please read
On Thursday 15 May 2008, Joshua Minor wrote: Can you clarify whether keys generated on an XO need to be regenerated or not. -josh If you are running a standard OLPC build no. Fedora is not effected by this bug only debian and debian based distros like Ubuntu and Knoppix. The standard OLPC build is based on Fedora and is not susceptible. however if you put a debian based distro on your XO then yes you will be susceptible. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: An OLPC Development Model
On Wednesday 07 May 2008, Bert Freudenberg wrote: On 07.05.2008, at 19:36, Marco Pesenti Gritti wrote: I'm not really convinced it should be a separate build. Just ship a set of core activities and make it really easy to install new ones (we have already everything in place to do so). I hate the core activities idea. What are the core activities for an education machine? The activities that distinguish the XO from all the other laptops out there are regularly omitted from the core. Like in the new olpc3 build (*). There is no technical reason for this, and it sends the wrong message. Unless someone wants to convey that this is just another laptop project. Quit making things out of nothing, the olpc3 builds are a start on getting builds based on F-9 nothing more nothing less. i branched pilgrim based on the joyride tree. right now im trying to get things to a state where the image boots. once it boots ill announce it from the top of every cliff please test.but until then do not read false things into it. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: An OLPC Development Model
On Wednesday 07 May 2008, Bert Freudenberg wrote: Well, my trust in OLPC is being probed every other day. I take your word, and I trust a few other people there, but I also have to acknowledge that priorities at OLPC are changing. So much so that some of the people I trusted most are leaving. And it's certainly no coincidence that the list of activities in olpc3 is what Kim wanted in ticket 6598. You certainly remember the discussions. We'll see. If this fear is unfunded, all the better. have you even looked at the build.log you would see Parsing package install arguments No package fonts-thai-ttf available. No package olpc-library-core available. No package olpc-library-common available. No package olpc-licenses available. No package squeak-vm available. No package etoys available. No package olpc-logos available. No package olpc-hardware-manager available. No package olpc-utils available. No package libabiword available. No package pyabiword available. No package libabiword-plugins available. No package GConf2-dbus available. No package hulahop available. Resolving Dependencies this is not because we dont want these things only that i'm trying to get built up a environment that will at least boot and allow for testing. the only reason ive not yet announced anything is because it doesnt boot let alone provide something that is useful for testing and moving forward. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: An OLPC Development Model
On Wednesday 07 May 2008, Bert Freudenberg wrote: On 07.05.2008, at 22:11, C. Scott Ananian wrote: And it's certainly no coincidence that the list of activities in olpc3 is what Kim wanted in ticket 6598. You certainly remember the discussions. You're on crack, Bert. *None* of the activities listed in 6598 are in the core build. Maybe I am hallucinating this: http://pilgrim.laptop.org/~pilgrim/olpc/streams/olpc3/build9/devel_jffs2/bu ild.log Installing Journal from file Journal-87.xo Installing Read from file Read-45.xo Installing Chat from file Chat-37.xo Installing Web from file Web-86.xo Installing Write from file Write-55.xo Installing Record from file Record-54.xo Installing Paint from file Paint-19.xo What was actually implemented was http://dev.laptop.org/ticket/2064, which I opened 10 months ago, and eventually prevailed with. joyride is the anomaly these days, mostly due to historical reasons and my personal laziness. Please open a bug against joyride if you feel strongly about it. I don't mind too strongly, but I filed a ticket anyway (#6966). the next joyride build and olpc3 build will only install Journal. signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: An OLPC Development Model
On Wednesday 07 May 2008, Chris Ball wrote: Hi, the next joyride build and olpc3 build will only install Journal. Oh, yuck. What's the recommended way for developers to install the activities, then? I don't think we're ready for this step -- the reason we still had all the activities in Joyride was that we don't have an activity that updates and installs activities yet. - Chris. Using the customisation key or one of the scripts floating around to install an activity bundle. they will be installed in /home then and its a one time deal. same as for update.1 http://wiki.laptop.org/go/Update_1 Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Browser on the XO
On Tuesday 06 May 2008, Tomeu Vizoso wrote: On 5/6/08, Ankita Prasad [EMAIL PROTECTED] wrote: Hi, I want to set up a linux machine with the exact browser which is on the XO. I have the correct xulrunner version. What else do I need in order to replicate the XO browser? Hi Ankita, if you are on Ubuntu, this may be easiest: http://wiki.laptop.org/go/Ubuntu#Option_3_-_Offical_Deb_Packages_for_Hardy_ LTS on fedora run yum install sugar telepathy-gabble then you can install the web activity into /usr/share/sugar/activities or ~/Activities soon you will be able to yum install sugar-web and have it just work. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Odd Libertas load error
On Thursday 01 May 2008, Martin Langhoff wrote:
Testing installation of a new build today with a hand-me-down Shuttle
machine I got a strange error from the Libertas driver.
libertas: version magic '2.6.23.1-21.fc7 SMP mod_unload 686 4KSTACKS '
should be '2.6.23.1-21.fc7 SMP mod_unload 586 4KSTACKS '
usb8xxx: version magic '2.6.23.1-21.fc7 SMP mod_unload 686 4KSTACKS '
should be '2.6.23.1-21.fc7 SMP mod_unload 586 4KSTACKS '
I repro'd this with 161, and (just in case) I tested downgrading the
firmware to the 160 version (usb8388-5.110.20.p49.bin). This is a P4
1.80GHz, I wonder if we are compiling the libertas driver with 686
flags?
cheers,
m
sounds like the i586 kernel is installed. can you try
rpm -q --queryformat %{name}-%{version}-%{release}.%{arch}\n kernel
kernel-smp and paste what you get
Dennis
signature.asc
Description: This is a digitally signed message part.
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel
Re: Fedora activities?
On Monday 28 April 2008, Bert Freudenberg wrote: On 26.04.2008, at 17:06, Kim Quirk wrote: Dennis Gilmore reports that we can now submit activities for review. Fedora 9 has working support in GDM/KDM to log into sugar. Draft guidelines can be found here: http://fedoraproject.org/wiki/DennisGilmore/SugarActivityGuidelines . The page does not exist. http://fedoraproject.org/wiki/Packaging/SugarActivityGuidelines it was moved to its final location They will be moved to the final location very soon. This will offer a great platform for developing activities. it will also help sugar be more accessible to people. Please package and submit your activity. Please ask Dennis if you have questions. What's the intent of this? That activities will be packaged and available in Fedora as rpms. so you will be able to log into sugar and develop activities and test in sugar without having an XO. It is also so that sugar can get wider use. The goal being that you can setup a sugar desktop for your children so that they can use it. I honestly hope that all distros follow suit and enable sugar as a desktop alternative. Dennis P.S. dont cc me on emails to lists. just reply to the list. I dont need to get the same email multiple times. signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fedora activities?
On Monday 28 April 2008, Bert Freudenberg wrote: On 28.04.2008, at 23:46, Dennis Gilmore wrote: On Monday 28 April 2008, Bert Freudenberg wrote: On 26.04.2008, at 17:06, Kim Quirk wrote: Dennis Gilmore reports that we can now submit activities for review. Fedora 9 has working support in GDM/KDM to log into sugar. Draft guidelines can be found here: http://fedoraproject.org/wiki/DennisGilmore/ SugarActivityGuidelines . The page does not exist. http://fedoraproject.org/wiki/Packaging/SugarActivityGuidelines it was moved to its final location I see. This: All Sugar Activities use setup.py is not accurate. I was misinformed then. when i asked i was told that they did. Ideally things like etoys and micropilis will use the same rpm thats used in other desktops for binaries. and there will be a small rpm that provides the sugar wrapper. for instance sugar-etoys would Require etoys and etoys would work exactly the same from KDE, Gnome and sugar. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XENified images for XO
On Thursday 10 April 2008, Marcus Leech wrote: Has anyone done any work on building XENified images for XO? I'm interested in this for building a large-scale virtualized XO environment for testing purposes. The other option is to run the XO image in HVM mode, but that limits which processors I can use to host such a thing. Cheers The work to do this is not trivial. however, im working on moving us to a Fedora-9 base. in doing so we should rebase the kernel. I understand dilinger has done alot of work to make sure we will be able to use 2.6.25 We should work with him to make sure that paravirt support in 2.6.25 is turned on. Of course you can use use what we have currently with full virt. but that does require cpu support/ or qemu which will slow things down. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: dropbox mechanism
On Friday 11 April 2008, Ricardo Carrano wrote: Hi! I want to include a new wireless firmware into joyride for testing (proper announcement will follow as soon as I find out how). It was suggested that I used the dropbox mechanism ( http://wiki.laptop.org/go/Build_system#Dropbox_Mechanism ). But the instructions are too succinct given my level of knowledge of git and OLPC's build process. Is someone in the list familiar with this? If so would this someone give me a hand? Thank you! Ricardo I will put the new firmware in if im notified of it. http://wiki.laptop.org/go/Firmware_release_procedures File a trac bug assign it to me user dgilmore and I will build it in koji. and get it pushed into joyride as well as updated in fedora. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Build Debate: Followup on Build Naming
On Thursday 10 April 2008, Charles Merriam wrote: Thanks for formalising this, I would also strongly suggest that the organisation is moved to the far right, and that we get rid of year. component major minor bugfix organisation I strongly suggest we keep the year. Yes, really, OLPC should release new software at least once per year. It should dump support for software two or more years old. It should release based on time, not feature. Also, why add a minor-minor (bugfix) number? I strongly feel that we should not put the year in releases. I personally think that we should use OLPC-Version.bugfix for the os so what has previously been called update.1 should be OLPC-2.0 any bug fixes based on this would be OLPC-2.1 etc Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Build Debate: Followup on Build Naming
On Monday 07 April 2008, Gary C Martin wrote: On 8 Apr 2008, at 04:53, Dennis Gilmore wrote: I honestly think we should call it OLPC 2 which matches the cvs/ build tag and signifies release number 2 OLPC 1 being ship.2 then we just increment the number for each stable release. we have a development codename of joyride. we can create a name for each release. Wouldn't OLPC 2 be new XO hardware? Just a gut feeling I get – but at least there's no damn date in there ;-) the hardware is XO-1 the next revison will be XO-2 the version of the OS that we have out when the next hardware revision comes out i would hope works on both sets of hardware. even if the hardware is a different architecture then i would hope we use the same source packages for both architectures. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Build Debate: Followup on Build Naming
On Monday 07 April 2008, Michael Stone wrote: cjb, cscott, and I just chatted about build names. We have absolutely no problem announcing official-703 (when candidate-703 becomes official) under whatever name seems good but we have no consensus about what that name should be. cscott proposes '8.1' on the basis that it will be our first 2008 release. mstone thought we should bake a month into the name (perhaps 2008.04 or April-2008). Scott strongly preferred to avoid baking a month designator into the name because, as best I understand, he thinks we cannot afford to ship another release until we've made 'enough' improvement in at least one of our (approximately) four networking scenarios. I honestly think we should call it OLPC 2 which matches the cvs/build tag and signifies release number 2 OLPC 1 being ship.2 then we just increment the number for each stable release. we have a development codename of joyride. we can create a name for each release. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Mini-conference schedule
On Wednesday 02 April 2008, C. Scott Ananian wrote: Here's a proposed schedule: Thursday (April 3) 12:30pm: Ben Schwartz, Frameworks for collaboration 1:30pm: Richard Smith, Suspend/Resume 2:30pm: Chris Ball, Power Management 3:30pm: break Lightning talks: 4:00pm - Eben Eliason, New Activity management design 4:30pm - Eben Eliason, Automatic transfer/update of activities 5:00pm - unowned, State of i18n (Edward Cherlin made original proposal; I'll summarize if no one volunteers) Friday (April 4): 12:30pm: C. Scott Ananian, olpcfs 1:30pm: April Fool, Build Process (I'll restate proposal made on devel@ if no one volunteers) 2:30pm: Dafydd Harries, Communications outlooks 3:30pm: break Lightning talks: 4:00pm - Martin Langhoff, State of the schoolserver 4:30pm - Eben Eliason: Toolbars (no) tabs 5:00pm - Michael Stone: State of security Can we have a dialin so that i can attend please Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Testing Update.1-702
On Wednesday 26 March 2008, you wrote: Dear everyone, At today's software status meeting, several individuals, including: dgilmore erikos bemasc Blaketh mstone volunteered [had their arms twisted] into running the http://wiki.laptop.org/go/1_Hour_Smoke_Test I ran through the smoke test today. I used update.1-703 I had one spanish and one english XO I had some keymap errors in X the console was fixed with the kbd update http://dev.laptop.org/ticket/6776 I had one issue with Read, Ive not yet filed a bug on it. I created a document in write. Put a picture in the middle with text on top. shared it between XO's. Which all worked fine. I copied to a usb key and opened on the the other XO. The image was left aligned. I wanted to repeat the test before filing a bug. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Defining where to store files in Java (and Python, Perl, etc) packages
On Tuesday 25 March 2008, Martin Langhoff wrote: On Mon, Mar 24, 2008 at 4:40 PM, Dennis Gilmore [EMAIL PROTECTED] wrote: As we are based on Fedora I suggest that we follow fedora's packaging guidelines. http://fedoraproject.org/wiki/Packaging/Guidelines The Java guidelines are currently being updated Agreed. When I looked at those yesterday I didn't see too much detail wrt paths and locations. The Debian guide has (imo stricter) path requirements, where possible, I'd follow those... :-) Fedora follows FHS guidelines http://fedoraproject.org/wiki/Packaging/Guidelines#head-e1c5548cbbe551c7a43d375c524ab2ea0188557e so everything is most likely to be in the same place. the macros used define FHS locations :) Dennis signature.asc Description: This is a digitally signed message part. ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: 1789 - sugar does not boot (1788 and 1790 either)
On Sunday 23 March 2008, Tomeu Vizoso wrote: On Mar 22, 2008, at 12:03 PM, Dennis Gilmore wrote: On Saturday 22 March 2008 11:52:47 am Michael Stone wrote: Examining http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html I suspect kbd-1.12-22 - 1.12-23 since we know that 1.12-23 (accidentally) contains an html file describing a spanish keyboard map instead of the map itself. does 1788 work for you? im wondering if libnl 1.1-1.fc7 is to blame. Yes, the libnl update seems to have broken things. -bash-3.2# NetworkManager --no-daemon NetworkManager: info starting... NetworkManager: symbol lookup error: NetworkManager: undefined symbol: nl_handle_alloc_nondefault ive just pulled the libdhcp and libnl updates so the next joyride build should be ok Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Update.1 build status
On Tuesday 11 March 2008, Dennis Gilmore wrote: There will not be a new build tonight. I need to know what sugar build we need pulled in. We need to have at least a patch applied for http://dev.laptop.org/ticket/6671 and http://dev.laptop.org/ticket/5933 I would be really nice to also have http://dev.laptop.org/ticket/6405 and http://dev.laptop.org/ticket/6170 fixed and we should really consider http://dev.laptop.org/ticket/6299 I also need to know exactly what activities we will be putting in the build. I have put going to go to get my Visa off until Monday the 17th so that we can get a build done in the morning. Dennis We Need to have a ticket file and assigned to ApprovalForUpdate for sugar. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Update.1 build status
There will not be a new build tonight. I need to know what sugar build we need pulled in. We need to have at least a patch applied for http://dev.laptop.org/ticket/6671 and http://dev.laptop.org/ticket/5933 I would be really nice to also have http://dev.laptop.org/ticket/6405 and http://dev.laptop.org/ticket/6170 fixed and we should really consider http://dev.laptop.org/ticket/6299 I also need to know exactly what activities we will be putting in the build. I have put going to go to get my Visa off until Monday the 17th so that we can get a build done in the morning. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 694 (TamTam?)
The process for getting things into update.1 has always been defined http://wiki.laptop.org/go/Update.1_process I did a quick search and it looks like you did not follow this process when requesting update. http://dev.laptop.org/ticket/6521 seems to be the ticket requesting their inclusion Please list in it exactly the files you want included and assign to ApprovalForUpdate Dennis On Wednesday 27 February 2008, Jean Piche wrote: Hello, Why are old TamTam builds still being used for update.1 builds, thereby not including current .po files? uptodate versions (and in curent joyride) are: TamTamEdit = 47 TamTamMini = 46 TamTamSynthLab = 48 TamTamJam = 48 according build.log, versions in last build (694) are: TamTamEdit = 45 TamTamMini = 44 TamTamSynthLab = 46 TamTamJam = 46 Weren't the requests from Jim to rebuild for inclusion of new .po files? jp (ethrop) On 26-Feb-08, at 5:40 PM, Build Announcer v2 wrote: http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build694 Changes in build 694 from build: 693 Size delta: 0.26M -etoys 2.3.1894-1 +etoys 2.3.1894-2 -telepathy-salut 0.2.2-1.olpc2 +telepathy-salut 0.2.2-3.olpc2 -Read 41 +Read 44 --- Changes for etoys 2.3.1894-2 from 2.3.1894-1 --- + respin rpm, previous etoys.image was broken (#6548) --- Changes for telepathy-salut 0.2.2-3.olpc2 from 0.2.2-1.olpc2 --- + dev.laptop.org #6483 for stream tube flushing (patch really applied) + dev.laptop.org #6483 for stream tube flushing (patch applied) --- Changes for Read 44 from 41 --- + fix unused_download_tubes problem, #6540 (gdesmott) + Pickup translations + Add mimetypes for djvu/tiff -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/update.1-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Preparing the XOs for next week's test
On Sunday 24 February 2008, Giannis Galanis wrote: Kim, You can see the diffs here: http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html http://dev.laptop.org/%7Erwh/announcer/joyride_vs_update1.html You will see that there are plenty of new stuff in joyride than just a telepathy-salut update. One thing we can do is use 693 and install the specific package, or make a new Update.1 build that includes it. But we should test it individually before putting it in the update.1 build. One thing we can do is have half the XOs with 1721 in one channel, and the other half with 693 in another channel. So we need a new read package and a new telepathy-salut. Giannis can you please make sure we have a trac bug filled requesting these. Who do i need to talk to to get the Read build done? Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 692
On Thursday 14 February 2008, Build Announcer v2 wrote: http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build692 Changes in build 692 from build: 691 This is an intrim build. some more updates were approved at the end of me putting together this build. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Items for update.1 RC3
So far i have to following updates to apply for update.1 Record-52.xo http://dev.laptop.org/ticket/4525 xkeyboard-config-1.1-11.20071130cvs.olpc2 http://dev.laptop.org/ticket/6159 sugar-0.75.12-1.olpc2 sugar-base-0.2.3-1.olpc2 http://dev.laptop.org/ticket/6381 etoys-2.3.1890-1.noarch.rpm Etoys-77.xo http://dev.laptop.org/ticket/6312 olpc-library-common-1-21 olpc-library-core-1-22 http://dev.laptop.org/ticket/6328 Journal-86.xo http://dev.laptop.org/ticket/6384 Memorize-25.xo http://dev.laptop.org/ticket/6401 AcousticMeasure-12.xo http://dev.laptop.org/ticket/6404 Chat-35.xo http://dev.laptop.org/ticket/6066 telepathy-salut-0.2.2-1.olpc2 http://dev.laptop.org/ticket/6271 kernel-2.6.22-20080211.1.olpc.9f4e619336a08dc http://dev.laptop.org/ticket/6402 sugar-0.75.13-1.olpc2 http://dev.laptop.org/ticket/6416 not all activities have been updated for new translations yet. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 691
On Friday 08 February 2008, Jim Gettys wrote: An updated etoys to pick up as much Spanish (and other languages) as we can will is definitely necessary; whether we call this update.1 RC3 or update.1.1 is all the same to me: updating all the activities to pick up the languages is in the immediate future. - Jim On Fri, 2008-02-08 at 08:56 -0600, Dennis Gilmore wrote: On Friday 08 February 2008, Bert Freudenberg wrote: Am Feb 8, 2008 um 0:46 schrieb C. Scott Ananian [EMAIL PROTECTED]: 2008/2/7 ffm [EMAIL PROTECTED]: I take it this is RC2? Does WEP work yet? This will be RC2 This cannot possibly be RC2 because not all approved packages are in. Etoys for example. I held etoys out because i dont know what critical bug it fixes. Dennis That is a perfectly acceptable reason the bug report did not state anything other than please include it. It will get picked up in the next build along with all the other translations. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 691
On Friday 08 February 2008, Bert Freudenberg wrote: Am Feb 8, 2008 um 0:46 schrieb C. Scott Ananian [EMAIL PROTECTED]: 2008/2/7 ffm [EMAIL PROTECTED]: I take it this is RC2? Does WEP work yet? This will be RC2 This cannot possibly be RC2 because not all approved packages are in. Etoys for example. I held etoys out because i dont know what critical bug it fixes. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [sugar] What's left for Update.1
On Thursday 31 January 2008, Jim Gettys wrote: For comment and discussion, here are the showstoppers I know of for getting Update.1 finished. If you think there are others, please speak up now (and modify the subject line to start another thread). Activity developers: note we'll be asking you to upload updated activities to pick up all the recent flurry of translation work very soon. 1 - wireless firmware and driver support (to fix problems with WEP and WPA) 2 - q2d11 OFW - to fix battery problems 3 - update activities to pick up translation work, Spanish in particular, but not missing other languages we may need. 4 - UI fix for registration with the school server. http://dev.laptop.org/ticket/6136 5 - switch to gabble from salut at school. 6 -testing and fixing anything critical! If we don't want to hold up an RC2 to pick up translation, then we should anticipate an RC4 might be necessary (as we may have issues that come up with updated activities). I think we will need a RC-4 Right now im waiting for tickets indicating which kernel and bootfw we need to use. Then I want to get a build out. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 690
On Friday 25 January 2008, Build Announcer v2 wrote: http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build690 Changes in build 690 from build: 689 Size delta: 0M -ohm 0.1.1-6.4.20080119git.fc7 +ohm 0.1.1-6.6.20080119git.fc7 -bootfw q2d08a-1.olpc2 +bootfw q2d10-1.olpc2.unsigned This is the intended update1 rc1 build. Please give this extensive testing Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 686
On Tuesday 22 January 2008, Build Announcer v2 wrote: http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build686 Changes in build 686 from build: 685 there is a build 687 on its way. the only change being that we will use the olpc.fth from bootfw not the one pilgrim wrote to the filesystem. This will update your firmware to the new version. So when you update reboot while still connected to power. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 1574
On Tuesday 22 January 2008, Build Announcer v2 wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1574 Changes in build 1574 from build: 1570 Size delta: 0M -ohm 0.1.1-6.4.20080119git.fc7 +ohm 0.1.1-6.5.20080119git.fc7 -bootfw q2d09-3.olpc2.unsigned +bootfw q2d07-0 --- Changes for ohm 0.1.1-6.5.20080119git.fc7 from 0.1.1-6.4.20080119git.fc7 --- + Fix a regression: we should never dim the screen when a tty is active. Please dont use this build. a build with bootfw-q2d09-3.olpc2.unsigned back in will be out soon Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Switch to a sane packaging and upgrade system
On Thursday 17 January 2008, Bernardo Innocenti wrote: C. Scott Ananian wrote: My thoughts are that I would like to write a yum post-install hook which stashed a copy of the RPMs installed to /home/olpc/.rpmcache. A post-upgrade hook (in olpc-configure) would attempt to reinstall all rpms found in /home/olpc/.rpmcache. This would address this common use-case (as well as my own: I keep having to re-install emacs). Yum already downloads all the rpms in /var/lib/yum/dist/packages. I don't think we need to do anything special. they get stored in /var/cache/yum/repo/packages though we clean up afterwards and dont keep the cache. Volunteers to write the yum hook welcome; the post-upgrade hook is simple. I don't think it's necessary. If a yum update gets interrupted, there are two possibilities: 1) the system does not boot any more 2) the system boots normally In (1), you need to reflash or boot from an older snapshot. In case (2), you could resume yum normally and it will not even need to download any packages. But you could as well do (1). if you got through installing everything before the interruption there is a yum-complete-transaction command that will finish the job. So my proposal is: let's extract the checkpointing code from olpc-update and use it as a wrapper for invoking yum. safe-yum? It should be much easier and safer. The downsides of using yum remains that it's a real memory hog and it will take additional disk space for all the rpms. Developers can learn to get around these limitations, but automated upgrades would fail very frequently due to these problems. yum cleans up its packages after its done the transaction how we have it configured A very effective solution is reducing the number of packages that yum has to deal with. Fedora is around 11 *thousand* packages. OLPC ships with 450. Clearly, we could save a lot of time and memory by disabling the huge Fedora repository. Dennis, what do you think? Having a smaller package set would greatly reduce yums overhead We can provide a disabled yum config pointing to a repo of everything. a developer can easily enable it. One thing we MUST do is not point our yum to koji.fedoraproject.org it needs to be pointed at a mirror list not a heavily loaded server. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 1538
On Tuesday 15 January 2008, Dennis Gilmore wrote: On Tuesday 15 January 2008, Benjamin M. Schwartz wrote: On Tue, 2008-01-15 at 13:45 -0500, Build Announcer Script wrote: +make.i386 1:3.81-6.fc7 +openldap-servers.i386 0:2.3.34-4.fc7 +perl.i386 4:5.8.8-27.fc7 +perl-libs.i386 4:5.8.8-27.fc7 Perl? Really? Ive had a look at what happened here the dhcp update from fedora adds an ldap schema that added a dependancy on openldap-servers that pulled in perl. I am working on getting that fixed. Dennis Ive made dhcp go back to the previous version. so these will fall out of the next build. it was not a security fix but fixed up support for storing dhcp data in ldap. NetworkManager requires dhcp currently so that an XO can act as a mesh portal. This is currently not enabled. for update.2 we would like to enable it and use dnsmasq as the dhcp server. ive opened http://dev.laptop.org/ticket/6028 to track this. It is something that will take some work to get implemented and working correctly. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 682
On Tuesday 15 January 2008, ffm wrote: What is stopping http://dev.laptop.org/~bert/update.1-joyride.html from being nil? What you pasted was out of date. joyride has many more activites than update.1 --- update.1/682 +++ joyride/1538 +blas.i386 0:3.1.1-1.fc7 blas provides libblas.so.3 which is needed by numpy in update.1 its provided by atlas which is also in joyride they put it in seperate locations. so they do not conflict. we do not make blas available to update.1 builds. -bootanim.i386 0:0.12-0 +bootanim.i386 0:0.13-0 This wont go in util i have the srpm that created the package +CartoonBuilder-1.xo +ClockActivity-3.xo +Connect-20.xo Extra Activities -dhclient.i386 12:3.0.5-40.fc7 +dhclient.i386 12:3.0.5-42.fc7 -dhcp.i386 12:3.0.5-40.fc7 +dhcp.i386 12:3.0.5-42.fc7 dhcp is getting reverted the update pulled in things we dont need and is not a security fix +FlipSticks-1.xo +Gmail-2.xo +JigsawPuzzle-2.xo +JokeMachine-6.xo Extra Activites -Journal-82.xo +Journal-83.xo No bug to update the activity -kernel.i586 0:2.6.22-20080107.1.olpc.4f7066ad642f673 +kernel.i586 0:2.6.22-20080110.1.olpc.940c801838dbaf2 will be updating shortly +LearningCenter-3.xo Extra Activites -libdhcp4client.i386 12:3.0.5-40.fc7 +libdhcp4client.i386 12:3.0.5-42.fc7 New Fedora update to be pulled -libutempter.i386 0:1.1.4-3.fc6 +libutempter.i386 0:1.1.5-1.fc7 New Fedora update +make.i386 1:3.81-6.fc7 pulled in as extra +MaMaMediaMenu-2.xo Extra Activites -olpccontents.i386 0:1.8-0 +olpccontents.i386 0:2.0-0 This wont go in util i have the srpm that created the package -olpc-library-common.noarch 0:1-15 +olpc-library-common.noarch 0:1-16 -olpc-library-core.noarch 0:1-16 +olpc-library-core.noarch 0:1-17 No request to update the packages -olpcrd.i386 0:0.37-0 +olpcrd.i386 0:0.39-0 -olpcupdate.i386 0:1.9-0 +olpcupdate.i386 0:2.1-0 This wont go in util i have the srpm that created the package +openldap-servers.i386 0:2.3.34-4.fc7 +perl.i386 4:5.8.8-27.fc7 +perl-libs.i386 4:5.8.8-27.fc7 Extra deps going to fall out +Poll-16.xo +SliderPuzzle-4.xo +WikiBrowse-9.xo Extra Activites +xorg-x11-drv-evdev.i386 0:1.2.0-2norel.olpc2 -xorg-x11-drv-evdev.i386 0:1.2.0-2.olpc2 I have just removed all of the old handbuilt X rpms from the tree used to create the olpc only side of the distro. the wrong version was getting pulled into update 1 because it was considered newer acording to rpm +xorg-x11-drv-keyboard.i386 0:1.1.0-3.fc7 -xorg-x11-drv-keyboard.i386 0:1.2.1-0.olpc2 +xorg-x11-drv-mouse.i386 0:1.2.1-2.fc7 -xorg-x11-drv-mouse.i386 0:1.2.2-0.olpc2 These are no longer used im waiting for a ticket from bernie so that they can be dropped from the image I hope this explains things Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 680
On Thursday 10 January 2008, ffm wrote: Are we in the RC stages now? When should QA start? -ffm Right now im syncing up joyride and update1 Please start doing extensive testing of update.1 builds and file bugs Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 676
On Wednesday 09 January 2008, Mikus Grinbergs wrote: Have 674. Don't quite know if this is equivalent or not, but instead of doing 'olpc-update' for 675 and 676, I've just been using 'yum update'. Seems to upgrade the same modules as the new builds. that will work for everything except activities which are not shipped as rpms Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Is joyride broken?
On Wednesday 02 January 2008, Bernardo Innocenti wrote: Bert Freudenberg wrote: Btw, pilgrim.laptop.org seems to be down ... Again? We had a short (0.5sec) power outage at 1CC a few days ago. Some machines which are not under UPS may have died. Someone please check pilgrim in the server room. httpd on pilgrim was not set to start on boot. ive corrected that and started it. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update1 build 630
On Monday 12 November 2007, Bert Freudenberg wrote: Btw, this diff is actually relative to build 625. - Bert - On Nov 12, 2007, at 6:57 , Build Announcer Script wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/update1/build630/ devel_jffs2/ For one this is not the right place for update1 builds and two we are up to build 669. What did you do here? Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update1 build 630
On Wednesday 02 January 2008, Dennis Gilmore wrote: On Monday 12 November 2007, Bert Freudenberg wrote: Btw, this diff is actually relative to build 625. - Bert - On Nov 12, 2007, at 6:57 , Build Announcer Script wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/update1/build630/ devel_jffs2/ For one this is not the right place for update1 builds and two we are up to build 669. What did you do here? Sorry the reply to this builds push messed me up. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Is the yum repository down?
On Saturday 29 December 2007, M. Edward (Ed) Borasky wrote: I just built a VMware virtual XO (build 655) and I can't seem to access the yum repositories: -bash-3.2# yum search chess http://mock.laptop.org/repos/local.ship2/repodata/repomd.xml: [Errno 12] Timeout: urlopen error timed out Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: olpc_local-ship2. Please verify its path and try again -bash-3.2# I haven't put my real XO on the network today -- too busy crawling around under my work table dealing with useless KVM switches. ;) But I can't think of any reason why this shouldn't work. P.S.: wget on the host is also not happy: $ wget http://mock.laptop.org/repos/local.ship2/repodata/repomd.xml --18:30:46-- http://mock.laptop.org/repos/local.ship2/repodata/repomd.xml = `repomd.xml' Resolving mock.laptop.org... 18.85.46.52 Connecting to mock.laptop.org|18.85.46.52|:80... failed: Connection refused. try now you should be fine lighttpd was not set to start on reboot and someone rebooted the box. it is now fixed. Dennis ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [PATCH] Re: DONT USE 1432 Re: New joyride build 1432
On Monday 17 December 2007, Bernardo Innocenti wrote: C. Scott Ananian wrote: On Dec 16, 2007 7:14 PM, Bernardo Innocenti [EMAIL PROTECTED] wrote: The new-kernel-pkg script is part of mkinitrd :-( Please, allow me some time to come up with a straightforward fix that doesn't require putting mkinitrd back in the builds. Can you please do this in your private builds, and not break joyride for the rest of us? I apologize, that was of course totally unexpected. Anyway, both my private builds and joyride are currently broken due to missing static repos in Fedora's Koji: Parsing package install arguments http://koji.fedoraproject.org/static-repos/dist-olpc2-build-current/i386/re podata/repomd.xml: [Errno 14] HTTP Error 403: Forbidden Trying other mirror. Error: Cannot open/read repomd.xml file for repository: olpc_development Dennis, do you have any idea what happened? the script that makes them got missed in the buildsys upgrade yesterday. it is now fixed. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Recent Joyride builds busted bad
On Monday 17 December 2007, Bernardo Innocenti wrote: On 12/17/07 20:42, Marcus Leech wrote: So, things like find and cpio were only listed as dependencies of mkinitrd, and not in any other packages? That's really weird! I guess these packages were so pervasively present everywhere that nobody even bothered to specify them explicitly. you only explicity Require packages you need to run. on my system for instance [EMAIL PROTECTED] ~]$ rpm -q --whatrequires findutils mkinitrd-6.0.19-4.fc8 java-1.5.0-gcj-1.5.0.0-17.fc8 man-1.6e-3.fc7 prelink-0.4.0-1 rpm-build-4.4.2.2-7.fc8 rpmdevtools-6.4-1.fc8 so we dropped mkinitrd we dont use java we dont provide man we are not prelinking and we dont provide utilities for building rpm. it is a similiar story for tar gzip bzip2 cpio So because we strip things down we need a way for useful standard utilities. I would suggest that we include everything we really want in pilgrim explicitly or we add them as Requires for olpc-utils ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 659
On Tuesday 18 December 2007, Build Announcer Script wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/update.1/build659/ The url is http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build659/ -Memorize-21.xo +Memorize-22.xo -Paint-12.xo +Paint-13.xo -Record-44.xo +Record-47.xo -cairo.i386 0:1.4.10-1.fc7 +cairo.i386 0:1.4.12-1.fc7 -hulahop.i386 0:0.3-1.olpc2 +hulahop.i386 0:0.4.0-1.olpc2 -olpcrd.i386 0:0.36-0 +olpcrd.i386 0:0.37-0 -olpcupdate.i386 0:1.7-0 +olpcupdate.i386 0:1.9-0 -telepathy-gabble.i386 0:0.7.1-0.7.olpc2 +telepathy-gabble.i386 0:0.7.1-0.8.olpc2 -telepathy-salut.i386 0:0.2.0-1.olpc2 +telepathy-salut.i386 0:0.2.0-2.olpc2 --- Memorize-22 --- * Brought the drumgit game back (erikos) * Release sound device when not in focus (erikos) --- Paint-13 --- * Updated POT file (using 'setup.py genpot') * Bug #3709 fixed; Right click only works with 'selection' and 'free polygon' * Fixed bug with free polygon * Bug #3703 fixed; 'Crtl+A' select all and 'Crtl+D' deselect, without buttons * Bug #3702 fixed; 'Erase' delete selection, 'return' confirm the selection --- Record-47 --- * #5448 fixes -- This email was automatically generated Aggregated logs at http://dev.laptop.org/~bert/update.1-pkgs.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 1401
On Tuesday 11 December 2007, Build Announcer Script wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1401/ +olpc-utils.i386 0:0.53-1.olpc2 -olpc-utils.i386 0:0.54-1.olpc2 +xorg-x11-drv-cirrus.i386 0:1.1.0-3.fc7 -xorg-x11-drv-cirrus.i386 0:1.1.0-5.olpc2 olpc-utils was reverted because it was causing us to not be able to build any packages. Dennis signature.asc Description: This is a digitally signed message part. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
