[Python-apps-team] Bug#906335: alot bug #906335

[Johannes Schauer]

Hi Santiago,

Quoting Santiago Vila (2018-08-25 12:38:08)
> > Santiago, how were you able to reproduce the issue?
> My building environment is described here:
> 
> https://people.debian.org/~sanvila/my-building-environment.txt
> 
> but to summarize: I'm using single-CPU KVM virtual machines running
> Debian stable, with sbuild and schroot. I'm using the "default" profile
> of schroot, so the contents of this file applies:
> 
> /etc/schroot/default/fstab
> 
> I believed the following line could be relevant, it says that /tmp in
> the chroot is bind-mounted from /tmp in the host machine:
> 
> /tmp            /tmp            none    rw,bind         0       0
> 
> But unfortunately, commenting out the line does not make the problem
> to disapear.
> 
> I guess I could prepare a virtual machine for any of you to reproduce
> the problem (please contact me privately for details).

yes, that would be helpful.

For what it's worth, here is a step by step instruction how to build alot in a
Stretch container for unstable *without* running into the FTBFS:

$ sudo debootstrap --include dbus stretch debian-stretch
$ sudo systemd-nspawn --boot --directory=debian-stretch

Then in a different terminal:

$ sudo machinectl shell debian-stretch /bin/bash
$ apt update
$ apt install sbuild schroot debootstrap --no-install-recommends
$ sbuild-createchroot unstable /srv/chroot/unstable-amd64 http://deb.debian.org/debian
$ sbuild -d unstable --arch-all alot

Builds successfully.

The question is: Which modifications do I have to do on this setup to trigger
the FTBFS?

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/python-apps-team/attachments/20180825/59424f76/attachment.sig>