[Pkg-ltsp-devel] Bug#539116: ltsp-server: garbage in output of ltsp-build-client

[Vagrant Cascadian]

On Wed, Jul 29, 2009 at 10:41:57AM +0200, Andre Majorel wrote:
> Package: ltsp-server
> Version: 5.1.73-1
> Severity: normal

i'm guessing it wouldn't make any difference, but it would be good to test with
a version of ltsp that is currently present in the archive.

> running ltsp-build-client &>log creates a file containing a long
> run of NULs and possibly out of order text :
> 
>   http://www.teaser.fr/~amajorel/bugs/ltsp-build-client-sid1.out.gz

wget  http://www.teaser.fr/~amajorel/bugs/ltsp-build-client-sid1.out.gz
--2009-07-29 11:14:19--  http://www.teaser.fr/~amajorel/bugs/ltsp-build-client-sid1.out.gz
Resolving www.teaser.fr... 213.162.54.69
Connecting to www.teaser.fr|213.162.54.69|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2009-07-29 11:14:20 ERROR 403: Forbidden.

the other URLs also give 403 errors.

> I'm guessing that at some point, something inside
> ltsp-build-client does something it shouldn't with stdout and/or
> stderr... Perhaps reopening either one with O_TRUNC just before
> writing "NOTE: disabling security APT source for sid.  It does not
> exist."...

ltsp-build-client doesn't really do anything unusual- it largely calls
debootstrap and apt in a chroot environment, and makes some edits to files.

could you try and reproduce the errors just using debootstrap, and if that
doesn't produce the same problem, chroot into it and run apt-get install
somepackages, and see if that reproduces the problem?

it would also be really nice to get actual version information from the server
where you've run ltsp-build-client. you can do this by running reportbug on the
server, and if necessary, cutting and pasting the resulting text.

live well,
  vagrant