reassign 598094 lsb-release affects 598094 ltsp-server thanks On Sun, Sep 26, 2010 at 01:24:15PM +0200, Siegfried wrote: > #ltsp-build-client > Traceback (most recent call last): > File "/usr/bin/lsb_release", line 96, in <module> > main() > File "/usr/bin/lsb_release", line 60, in main > distinfo = lsb_release.get_distro_information() > File "/usr/lib/pymodules/python2.6/lsb_release.py", line 271, in > get_distro_information > distinfo = guess_debian_release() > File "/usr/lib/pymodules/python2.6/lsb_release.py", line 225, in > guess_debian_release > rinfo = guess_release_from_apt() > File "/usr/lib/pymodules/python2.6/lsb_release.py", line 179, in > guess_release_from_apt > releases.sort(cmp = lambda x,y: RELEASES_ORDER.index(y[1]['suite']) - > RELEASES_ORDER.index(x[1]['suite'])) > File "/usr/lib/pymodules/python2.6/lsb_release.py", line 179, in <lambda> > releases.sort(cmp = lambda x,y: RELEASES_ORDER.index(y[1]['suite']) - > RELEASES_ORDER.index(x[1]['suite'])) > ValueError: list.index(x): x not in list > /usr/share/ltsp/plugins/ltsp-build-client/common/010-chroot-tagging: Zeile 3: > /opt/ltsp/amd64/etc/ltsp_chroot: Datei oder Verzeichnis nicht gefunden > Fehler: Die LTSP-Client-Installation ist fehlgeschlagen > #
ltsp-build-client is calling "lsb_release --id --short". i've seen lsb_release fail before, but not that badly. my *guess* is something odd with your apt configuration... do you have in your source.list from third party vendors (i.e. not from *.debian.org mirrors)? live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
