On Mon, Jul 09, 2018 at 01:42:08AM -0500, Dirk Eddelbuettel wrote:
>
> On 9 July 2018 at 08:02, Santiago Vila wrote:
> | On Sun, Jul 08, 2018 at 09:36:13PM -0500, Dirk Eddelbuettel wrote:
> |
> | > Seems to work here,
> |
> | Please try "sbuild --arch-any --no-arch-all" on a clean chroot,
> | which is what an official autobuilder would do.
> |
> | I can't test an external package easily, and I think it is much better
> | if you can reproduce the bug before trying a fix.
>
> By now taken care of -- and as I am pbuilder user the sbuild hint does not
> help as much.
The equivalent in pbuilder would be --binary-arch. From the manpage:
Specify to build only architecture specific targets instead of all targets.
This instructs pbuilder to respect only Build-Depends,
Build-Depends-Arch, Build-Conflicts, Build-Conflicts-Arch source
relationships, and calls dpkg-buildpackage with -B.
Sometimes there are differences between "dpkg-buildpackage -B" and
plain "dpkg-buildpackage".
However, this does not seem to be the case here.
This package (jags) has proved to be reproducible, and the
reproducible builds autobuilders use pbuilder as well,
so if you see a failure to build in buster here:
https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/jags.html
and it builds fine in your system, chances are that you are doing
something wrong. My bet would be that your chroot is not up to date,
as this issue started happening recently, with debhelper 11.3.5.
> I added mercurial, and fixed one tex issue, so -2 should fare
> better.
I've checked and it builds fine here now.
Thanks a lot.
