[Server-devel] XS 0.5 upgrade notes

[Greg Smith]

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" 
<martin.langhoff at gmail.com> Subject: Re: [Server-devel] XS 0.5 upgrade 
notes To: "Douglas Bagnall" <douglas at paradise.net.nz> Cc: server-devel 
<server-devel at lists.laptop.org> Message-ID: 
<46a038f90811120726x2a54e506ndd75535a0ec136ae at mail.gmail.com> 
Content-Type: text/plain; charset=ISO-8859-1 On Wed, Nov 12, 2008 at 
12:31 AM, Douglas Bagnall <douglas at paradise.net.nz> 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:
 > >
 > > [root at schoolserver1 ~]# yum repolist
 > > repo id              repo name                                status
 > > 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
-- martin.langhoff at gmail.com martin at laptop.org -- School Server 
Architect - ask interesting questions - don't get distracted with shiny 
stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff