On Mon, Feb 23, 2009 at 09:44, Jonas Smedegaard <d...@jones.dk> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, Feb 23, 2009 at 09:02:53AM +0100, Bert Freudenberg wrote: >> >>On 23.02.2009, at 01:33, Gary C Martin wrote: >> >>> On 22 Feb 2009, at 23:22, Caroline Meeks wrote: >>> >>>> How will I know what snapshot I have on a given USB so that I can >>>> accurately report bugs? >>> >>> Hi Caroline, if you have a peek in the directory: >>> >>> http://download.sugarlabs.org/soas/snapshots/1/ >>> >>> You'll see that Soas-200902221746.iso (currently) has the same date >>> as latest.iso. >>> >>> I'm guessing there have been a bunch of pages and emails pointing to >>> some random .iso builds over time, that all need to be kept upto >>> date, pointing them to latest.iso will keep them all in sync in an >>> automated way. >>> >>> --Gary >> >> >> >>The question is, when I download "latest", and find a bug to report, >>how do I find out which SoaS image this was? "About my laptop" is >>unhelpful. >> >>I guess there needs to be a version file somewhere. > > I recommend that you treat Soas as a distribution on its own, and make > sure `lsb_release --all` reports info about your distro, not the one you > forked from. And that OLPC does the same with the XO images. > > And I recommend that Sugar - if it doesn't already - gets its "About > this system" from lsb_release.
Actually, the build number in the control panel is retrieved from /boot/olpc_build, /etc/redhat-release and lsb_release -ds. Regards, Tomeu _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel