[Bug 277331] Re: 'ltsp-build-client' should pull from *-updates repository by default
stuartiannaylor at hotmail.com
Sun Sep 16 09:07:17 UTC 2012
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)
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ltsp in Ubuntu.
'ltsp-build-client' should pull from *-updates repository by default
Status in Linux Terminal Server Project:
Status in “ltsp” package in Ubuntu:
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
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
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:
More information about the foundations-bugs