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

[Jordan Erickson]

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').

[Jordan Erickson (lns)]

To add a bit more information to this, here's what I did:

- Built a fresh chroot via "ltsp-build-client" (in an alternate dir /opt/ltsptest for testing)
- su
- echo "deb http://us.archive.ubuntu.com/ubuntu/ hardy-updates main restricted" >> /opt/ltsp/i386/etc/apt/sources.list
- chroot /opt/ltsptest
- apt-get update

And then....

# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-image-2.6.24-19-generic linux-ubuntu-modules-2.6.24-19-generic
The following packages will be upgraded:
  base-files bash bsdutils cpp dpkg eject file gtk2-engines-ubuntulooks initramfs-tools iproute klibc-utils libc6 libc6-i686 libcairo2 libdbus-1-3 libfreetype6 libglib2.0-0 libgnutls13 libgtk2.0-0
  libgtk2.0-common libhal1 libklibc libldap-2.4-2 libmagic1 libpam-modules libpam-runtime libpam0g libpango1.0-0 libpango1.0-common libpcre3 libssl0.9.8 libtiff4 linux-image-generic ltsp-client
  ltsp-client-core ltspfsd mount openssh-client pciutils procps python2.5 python2.5-minimal rdesktop sudo tzdata util-linux util-linux-locales x11-common xorg xserver-xorg xserver-xorg-core
  xserver-xorg-input-all xserver-xorg-video-all xserver-xorg-video-amd xserver-xorg-video-cirrus xserver-xorg-video-geode xserver-xorg-video-intel xserver-xorg-video-nsc
58 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 53.5MB of archives.
After this operation, 77.6MB of additional disk space will be used.
Do you want to continue [Y/n]?
---

Holy crap, 58 updated packages, including ltsp-client, ltsp-client-core, ltspfsd... I think we want those! :)

[Jordan Erickson (lns)]

Whoops...sorry, typo in the 'echo' line. I assure I was working with the same chroot the whole time.

[Warren Togami (wtogami)]

Sigh. Is it possible for people to report bugs against Ubuntu? This is not an upstream bug. I don't want to see reports like this that have nothing to do with me.

[Jordan Erickson (lns)]

Sorry Warren - I'm still getting used to the ropes on bug reporting and the difference between reporting to upstream projects vs. Ubuntu-specific projects via LP.

[Rob Owens (rob-owens)]

As a workaround, try running:

ltsp-build-client --copy-sourceslist

[Jordan Erickson (lns)]

Rob, thanks for that - this will work (as a workaround), provided the LTSP server has the *-updates repository enabled in its own sources.list.

I would really like to see this 'bug' fixed properly, however, provided it doesn't step on any Ubuntu policies regarding default repositories. The main reason I reported this in the first place was that my LTSP chroot was broken due to the NBD_SWAP default port bug (see description for bug link) being present in the default packages. It was only fixed in packages available in hardy-updates, which breaks every default LTSP installation without manual intervention to pull from the updates repo (even when using ltsp-build-client to build a brand new chroot). Shouldn't happen IMHO, and I'm sure a ton of admins have issues with LTSP (and are complaining on IRC, mailing lists, and LP) because of these (since fixed) bugs.

[Luis Montes (monteslu)]

I agree with Jordan on this.

The nbd bug caused me a ton of grief at a school that I volunteer for. Updating the chroot fixed the issue. I was surprised that the chroot doesn't already get updated when the server gets updated. What happens with security fixes?
I think this is a no brainer.

[Stéphane Graber (stgraber)]

That's now fixed in Karmic.

[StuartIanNaylor (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