[Bug 277331] Re: 'ltsp-build-client' should pull from *-updates repository by default

[StuartIanNaylor]

I am not sure if this is a bug or it purely allows you to enable the
repo's you require.

If you are going to ltsp-build-client --copy-sourceslist remember --apt-
keys aswell (point to trustedgpg)

Stuart

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ltsp in Ubuntu.
https://bugs.launchpad.net/bugs/277331

Title:
  'ltsp-build-client' should pull from *-updates repository by default

Status in Linux Terminal Server Project:
  Invalid
Status in “ltsp” package in Ubuntu:
  Fix Released

Bug description:
  When building an LTSP client chroot from scratch, 'ltsp-build-client'
  should pull packages from hardy-updates by default. Figuring out that
  it *wasn't* pulling committed hardy-updates during a clean chroot
  build was a tedious process for me, as I was relying on functionality
  that was present in the updated "ltsp-client-core" package (namely
  re:Bug #235772), but it was never present after a chroot re-build
  since hardy-updates was never enabled in the chroot's sources.list
  file.

  So, when 'ltsp-build-client' generates an
  /opt/ltsp/*/etc/apt/sources.list file, it should add -updates to the
  list. Right now, it only contains the following 2 repositories by
  default:

  ---
  deb http://archive.ubuntu.com/ubuntu hardy main restricted
  deb http://security.ubuntu.com//ubuntu hardy main restricted
  ---

  I think this might be a pretty widespread misconception regarding
  issues/bugs with LTSP and issues/bugs that have already been fixed,
  yet updates are never applied since the repos aren't in the chroot by
  default (and aren't pulled during a fresh 'ltsp-build-client').

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