On Sun, Jan 08, 2017 at 04:38:36PM +0100, John Paul Adrian Glaubitz wrote: > Control: user debian-al...@lists.debian.org > Control: usertags alpha > > > Apparently (see Bug #821332), I would need somebody having an alpha to > > check that "dpkg-buildpackage -A" works. > > I can actually do that, I have access to an alpha porterbox. However, you > can also actually do it yourself by setting up a qemu-based alpha chroot, > similar to this [1]. > > In any case, I'm adding debian-alpha@l.d.o to the discussion as the alpha > porters should actually be put in the loop here.
Even if "dpkg-buildpackage -A" works on alpha, that could be not enough. Our Arch:all autobuilder runs amd64, not alpha. What I would do here is to convert the package to a pure Arch:any or Arch:alpha package, without Arch:all tricks to distribute the files to other architectures. IMO, those who really need the files outside an alpha machine will figure out how to get them. Thanks.
