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. -- 'ltsp-build-client' should pull from *-updates repository by default https://bugs.launchpad.net/bugs/277331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
