[buildd-tools-devel] Bug#775091: sbuild: sbuild-updates creates two files in /tmp on every run

[Roger Leigh]

On 13/09/2015 16:24, Johannes Schauer wrote:
> Hi,
>
> Quoting Sebastian Ramacher (2015-09-13 16:01:48)
>> This is enough to reproduce it in jessie:
>>
>> $ sudo sbuild-createchroot \
>>    --make-sbuild-tarball=/tmp/test.tar.gz \
>>    sid `mktemp -d` \
>>    http://localhost:3142/debian # replace with your own mirror
>> $ tar taf /tmp/test.tar.gz ./tmp
>> ./tmp/
>> ./tmp/WCV3MjvRTJ
>> ./tmp/fbuo0WWY51
>> $ sudo sbuild-update -udrc sid-amd64-sbuild
>> $ tar taf /tmp/test.tar.gz ./tmp
>> ./tmp/
>> ./tmp/WCV3MjvRTJ
>> ./tmp/fbuo0WWY51
>> ./tmp/xstgwRr70t
>> ./tmp/6VSNh4CcCe
>>
>> Every run of sbuild-update adds to new files to /tmp in the tarball.
>
> that's what I tread earlier too but did not see what you see and still do not
> after trying again from scratch.
>
> Are you sure that you are not using some special schroot config which does not
> bind mount /tmp for example? (look into /etc/schroot/default/fstab)

Interesting.  The repacking of the tarfile should happen after all other 
filesystems are unmounted.  If not mounting /tmp causes cruft to be 
packed, then it would be useful to know

- what's creating the cruft
- if it would be useful to clean certain locations like /tmp before 
repacking


Regards,
Roger