epoptes team mailing list archive

[Chris Halse Rogers <raof@xxxxxxxxxx>]

Hello Alkis, or anyone else affected,

Accepted epoptes into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/epoptes/0.5.5-0ubuntu0.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from
verification-needed to verification-done.  If it does not, change the
tag to verification-failed.  In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: epoptes (Ubuntu Precise)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Epoptes
Developers, which is the registrant for Epoptes.
https://bugs.launchpad.net/bugs/1018498

Title:
  Ensure that epoptes-client is actually booted to ltsp before setting
  LTSP_FATCLIENT=True

Status in Epoptes:
  Fix Released
Status in “epoptes” package in Ubuntu:
  Fix Released
Status in “epoptes” source package in Precise:
  Fix Committed
Status in “epoptes” source package in Quantal:
  Fix Released

Bug description:
  Epoptes version: 0.5.3-1

  If one installs epoptes-client in a standalone (non-LTSP) PC which for
  some reason also has the ltsp-client package installed, then that PC
  is reported to be a fat client in the Epoptes UI, even if it was
  booted locally.

  == SRU ==
  [rational]
  Epoptes reports regular workstations with ltsp-client installed as fat clients even though they didn't boot from LTSP.

  [test case]
  1) Install epoptes
  2) Install ltsp-client
  3) Restart epoptes
  4) Start classroom manager on teacher computer

  4) should report the machine as a workstation, not a fat client

  [regression potential]
  The fix just adds a check for /proc/cmdline, the check while not perfect should match 99% of the cases where ltsp-client and epoptes are installed on a non-ltsp machine.
  If this still doesn't match, then the client will be reported as a fat client, but overall, the logic can't be any more wrong that it's today.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/1018498/+subscriptions