Re: [Server-devel] XS 0.5 upgrade notes
Martin Langhoff wrote: On Wed, Nov 12, 2008 at 12:10 PM, Jerry Vonau [EMAIL PROTECTED] wrote: Well, since /etc/yum.conf is provided by yum itself, there should of been a yum.conf.rpm(olpc?)new file created as not to overwrite our modified one. Ok - I've pushed out a new xs-config that should address the issue. The problem is that the yum.conf file in xs-0.4 was tampered with from a %post script. Nasty stuff, so the user 'hasn't changed it' but rpm things it's changed. There's a sane and safe workaround -- but your peer review is more than welcome -- in the new xs-config. Can you (or Douglas) confirm that the old file we want to replace has a sha1 of 2f12835cb11f100be169abcc8bff72525a25cff7 ? The patch is here: http://dev.laptop.org/git?p=projects/xs-config;a=commitdiff;h=b81ed4df7a1a534fcf8c2249e739a03def3c75dd Think the best way out of this is to have xs-release move/rename the current yum.conf file. Well, xs-release is doing the right thing, but the old xs-config made a mess of it all. Hmmm. Perhaps the patch I've done should be actually be placed in xs-release instead. Your fix should work fine. Since the topic of yum upgrades came up, is this support wanted? I'm thinking that this could be doable from the cdrom and/or across the net. Yes. I don't know if it's reasonable for a 0.4-0.5 upgrade as it's rather large and full of nasty odd corner cases. In other words, it may work but if it breaks I don't think it's worthwhile to fix it. Going forward 0.5-0.6-0.7 will probably be all F9 based so yum updates will be trivial. When we move to F10 or F11 we'll have to evaluate whether it's within reach. The good news is that the Fedora team seems to be interested in polishing the in place update machinery (which I assume is yum), so I want to ride on that wave if possible. I tried a yum .4 - .5, the change in the network scripts makes this rather unworkable, best to use anaconda here at least for .4 - .5. Using yum updates after .5 should be a non-issue. To help make this installation easier to use, we may want to define a group in the comps.xml file. This would allow you to install the xs-release rpm, to activate the repos, then do a yum groupinstall xs-school-server then your off and running... Is that better than xs-pkgs? Well, for anaconda, not really. For yum, the listing of the xs-* file with mandatory for our group would install the listed files when you use yum [groupinstall/groupupgrade] ourgroup . It's more like shorthand for yum install xs-config xs-pkgs xs-. Also should offer the chance not to install some packages that we my not want installed by default. My concern is that comps.xml is not modular AFAIK -- there is just one, so we can patch it, but then we'll want to merge with the upstream one. Yes, we can do it, but it seems awkward. I'm not clear on how we publish it either - does it become published as part of our repo? Yes, the changed comps.xml file becomes part of the repo when you use -g (to point to the edited comp file) with createrepo. Do we have to convince Fedora to carry our changes to comps.xml or users to download ours and point their yum config to it? Nether, the comps file would be merged with the stock one by yum. I'll need to review yum for anything that may of changed in respect to group handling when 2 comp files are present. IOWs, I understand how a metapackage works much better :-) I'll have some time to throw at this in a day or so, if there is any interest. Great to have you back on board! Just had other stuff on the front burner. Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 upgrade notes
On Wed, Nov 12, 2008 at 12:31 AM, Douglas Bagnall [EMAIL PROTECTED] wrote: Some issues noticed with an upgrade from XS 0.4 to a XS 0.5 candidate. 1. eth0 and eth1 swapped physical ports. After swapping the cables and `service network restart`, everything was good. Yeah, that's worthy of a release note commment, and a pointer to xs-swapnics which does the job too :-) I think Martin is working on #3. #4 is (theoretically) fixed. The others look WONTFIX-able. Agree. At this point I tried to yum upgrade to get changes I'd made since spinning the ISO, but nothing happened, because: [EMAIL PROTECTED] ~]# yum repolist repo id repo namestatus fedora Fedora 7 - i386 enabled : 7,382 olpc OLPC 7 - i386enabled : 83 updates Fedora 7 - i386 - Updatesenabled : 4,545 Yum still wants to use the XS 0.4 repos. This seems to be related to #8033 and the use of the alternate /etc/yum.repos.olpc.d/, but I'm not entirely sure of the solution. Ouch. So it's still using the old/bad yum config file? That'd be something to look into around the xs-config upgrade path where we try to fixup overwritten files. good spotting, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 upgrade notes
Martin Langhoff wrote: On Wed, Nov 12, 2008 at 12:31 AM, Douglas Bagnall [EMAIL PROTECTED] wrote: Some issues noticed with an upgrade from XS 0.4 to a XS 0.5 candidate. At this point I tried to yum upgrade to get changes I'd made since spinning the ISO, but nothing happened, because: [EMAIL PROTECTED] ~]# yum repolist repo id repo namestatus fedora Fedora 7 - i386 enabled : 7,382 olpc OLPC 7 - i386enabled : 83 updates Fedora 7 - i386 - Updatesenabled : 4,545 Yum still wants to use the XS 0.4 repos. This seems to be related to #8033 and the use of the alternate /etc/yum.repos.olpc.d/, but I'm not entirely sure of the solution. Ouch. So it's still using the old/bad yum config file? That'd be something to look into around the xs-config upgrade path where we try to fixup overwritten files. Well, since /etc/yum.conf is provided by yum itself, there should of been a yum.conf.rpm(olpc?)new file created as not to overwrite our modified one. Douglas, is there a new file present on your machine? I'm just a little short of time right now to recreate the steps, I don't have a 0.4 yum.conf file to look at right now, I can't recall other than repodir what was changed, could you post yours? There should be an upgrade.log dropped into /root by anaconda, mind if I have a look it? Think the best way out of this is to have xs-release move/rename the current yum.conf file. Yum should then install a pristine one, just need to check the installation order of the rpms from the above log file, just to be sure that yum installs after xs-release. This should smooth things over going forward. Since the topic of yum upgrades came up, is this support wanted? I'm thinking that this could be doable from the cdrom and/or across the net. At least a script that sources the cdrom as the repo to use while disabling the network based repos, then calls yum to do the upgrade. To help make this installation easier to use, we may want to define a group in the comps.xml file. This would allow you to install the xs-release rpm, to activate the repos, then do a yum groupinstall xs-school-server then your off and running... I'll have some time to throw at this in a day or so, if there is any interest. Jerry ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 upgrade notes
Hi Douglas and Martin, Good info! As Martin says, can we put that in the release notes? Also on release notes, I was poking around in GIT and came across a bunch of very useful looking Readme files. Can we copy those in to the release notes (or maybe link to them in GIT if they will stay the same)? I think that's all the documentation we will need for most features. Let me know how I can help with the mechanics of making the info available or with creating the release notes content. Thanks, Greg S Date: Wed, 12 Nov 2008 10:26:22 -0500 From: Martin Langhoff [EMAIL PROTECTED] Subject: Re: [Server-devel] XS 0.5 upgrade notes To: Douglas Bagnall [EMAIL PROTECTED] Cc: server-devel [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 On Wed, Nov 12, 2008 at 12:31 AM, Douglas Bagnall [EMAIL PROTECTED] wrote: Some issues noticed with an upgrade from XS 0.4 to a XS 0.5 candidate. 1. eth0 and eth1 swapped physical ports. After swapping the cables and `service network restart`, everything was good. Yeah, that's worthy of a release note commment, and a pointer to xs-swapnics which does the job too :-) I think Martin is working on #3. #4 is (theoretically) fixed. The others look WONTFIX-able. Agree. At this point I tried to yum upgrade to get changes I'd made since spinning the ISO, but nothing happened, because: [EMAIL PROTECTED] ~]# yum repolist repo id repo namestatus fedora Fedora 7 - i386 enabled : 7,382 olpc OLPC 7 - i386 enabled : 83 updates Fedora 7 - i386 - Updates enabled : 4,545 Yum still wants to use the XS 0.4 repos. This seems to be related to #8033 and the use of the alternate /etc/yum.repos.olpc.d/, but I'm not entirely sure of the solution. Ouch. So it's still using the old/bad yum config file? That'd be something to look into around the xs-config upgrade path where we try to fixup overwritten files. good spotting, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 upgrade notes
On Wed, Nov 12, 2008 at 12:27 PM, Greg Smith [EMAIL PROTECTED] wrote: As Martin says, can we put that in the release notes? I'll do that :-) Also on release notes, I was poking around in GIT and came across a bunch of very useful looking Readme files. Can we copy those in to the release notes (or maybe link to them in GIT if they will stay the same)? We can link in the Wiki directly to git content, and it appears 'inline'. See what we've done with http://wiki.laptop.org/go/XS_Automount_triggers cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS 0.5 upgrade notes
On Wed, Nov 12, 2008 at 12:10 PM, Jerry Vonau [EMAIL PROTECTED] wrote: Well, since /etc/yum.conf is provided by yum itself, there should of been a yum.conf.rpm(olpc?)new file created as not to overwrite our modified one. Ok - I've pushed out a new xs-config that should address the issue. The problem is that the yum.conf file in xs-0.4 was tampered with from a %post script. Nasty stuff, so the user 'hasn't changed it' but rpm things it's changed. There's a sane and safe workaround -- but your peer review is more than welcome -- in the new xs-config. Can you (or Douglas) confirm that the old file we want to replace has a sha1 of 2f12835cb11f100be169abcc8bff72525a25cff7 ? The patch is here: http://dev.laptop.org/git?p=projects/xs-config;a=commitdiff;h=b81ed4df7a1a534fcf8c2249e739a03def3c75dd Think the best way out of this is to have xs-release move/rename the current yum.conf file. Well, xs-release is doing the right thing, but the old xs-config made a mess of it all. Hmmm. Perhaps the patch I've done should be actually be placed in xs-release instead. Since the topic of yum upgrades came up, is this support wanted? I'm thinking that this could be doable from the cdrom and/or across the net. Yes. I don't know if it's reasonable for a 0.4-0.5 upgrade as it's rather large and full of nasty odd corner cases. In other words, it may work but if it breaks I don't think it's worthwhile to fix it. Going forward 0.5-0.6-0.7 will probably be all F9 based so yum updates will be trivial. When we move to F10 or F11 we'll have to evaluate whether it's within reach. The good news is that the Fedora team seems to be interested in polishing the in place update machinery (which I assume is yum), so I want to ride on that wave if possible. To help make this installation easier to use, we may want to define a group in the comps.xml file. This would allow you to install the xs-release rpm, to activate the repos, then do a yum groupinstall xs-school-server then your off and running... Is that better than xs-pkgs? My concern is that comps.xml is not modular AFAIK -- there is just one, so we can patch it, but then we'll want to merge with the upstream one. Yes, we can do it, but it seems awkward. I'm not clear on how we publish it either - does it become published as part of our repo? Do we have to convince Fedora to carry our changes to comps.xml or users to download ours and point their yum config to it? IOWs, I understand how a metapackage works much better :-) I'll have some time to throw at this in a day or so, if there is any interest. Great to have you back on board! cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
