Opened 15 years ago

Closed 15 years ago

Last modified 11 years ago

#76 closed enhancement (fixed)

Need a way to tell what .iso a SoaS was built from

Reported by: CarolineM Owned by: marcopg
Priority: High Milestone:
Component: Sugar on a Stick (SoaS) Version: Git as of bugdate
Severity: Minor Keywords:
Cc: Distribution/OS: Unspecified
Bug Status: Resolved


As we collect testing data we need a way from Sugar to know what build we are working with.

Change History (10)

comment:1 Changed 15 years ago by mungewell

For Ubuntu based systems:
It is convention to include an info file in the '.disk/' directory of the LiveCD;
$cat .disk/info
Ubuntu 8.10 "Intrepid Ibex" - Release i386 (20081029.5)

Whilst running the CD will be mounted under /cdrom, so look in '/cdrom/.disk/info'

This unfortunately won't help if you are creating the live disk by adding an additional squashfs archive to an existing CD. I'm not sure whether you can overwrite a file, or know which order the squashfs archives will be loaded.

The other problem is that a LiveCD/USB is actually a full system, given a large enough persitance file one could actually update the whole system to a newer release of the distribution (just an 'apt-get' away).

So an activity might actually be a newer release than that on the LiveCD/USB image/distribution.

The only sure fire way is to dump the package lists.... 'dpkg --list'.


comment:2 Changed 15 years ago by tomeu

  • Component changed from sugar-datastore to sugar
  • Owner changed from tomeu to marcopg
  • Status changed from new to assigned

I think this is more for Marco.

comment:3 Changed 15 years ago by tomeu

  • Bug Status set to Assigned
  • Component changed from sugar to SoaS
  • Distribution/OS set to Unspecified
  • Milestone set to 0.84
  • Severity set to Major
  • Version set to 0.83.x

comment:4 Changed 15 years ago by marcopg

This might actually be primarily a sugar bug, if we want something in the UI. Caroline, what do you think? I guess we might a control panel page about this (if I remember correctly there is already something XO specific that we should generalize).

comment:5 Changed 15 years ago by dfarning

The gnome->about panel has a nice Version, Distribution, Build panel that could used as a model to create consistency across various Sugar versions, distros, and builds for Sugar.

comment:6 Changed 15 years ago by CarolineM

yes, as Sugar goes everywhere we'll want this.

comment:7 Changed 15 years ago by CarolineM

  • Type changed from defect to enhancement

I think this is still an active request

comment:8 Changed 15 years ago by sdz

  • Bug Status changed from Assigned to Resolved
  • Distribution/OS changed from Unspecified to SoaS
  • Milestone changed from 0.84 to soas_v2
  • Priority changed from major to High
  • Resolution set to fixed
  • Severity changed from Major to Minor
  • Status changed from assigned to closed
  • Version changed from 0.83.x to Git as of bugdate

This is fixed in GIT now: We're displaying the date the image got composed in the "About my Computer" screen now. Will be in the next snapshot!

comment:9 Changed 14 years ago by sascha_silbe

  • Distribution/OS changed from SoaS to Unspecified

Bulk change distribution=SoaS -> component=SoaS

comment:10 Changed 11 years ago by dnarvaez

  • Milestone Blueberry deleted

Milestone Blueberry deleted

Note: See TracTickets for help on using tickets.