[Bug 1762890] Re: build fails in multi-arch environment (missing changes file)

[Mattia Rizzolo]

It's just that by default it is expecting the chroot to be of the same
architecture of the host system, unless instructed otherwise.

Fixed that particular case here of the .changes file, but I wouldn't be
surprised if anything else was doing same bad assumption.

https://salsa.debian.org/pbuilder-
team/pbuilder/commit/00c5ac2c9c12c2696d9c7834e1527feab9cdfbdf

** Changed in: pbuilder (Ubuntu)
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pbuilder in Ubuntu.
https://bugs.launchpad.net/bugs/1762890

Title:
  build fails in multi-arch environment (missing changes file)

Status in pbuilder package in Ubuntu:
  Fix Committed

Bug description:
  I've recently switched my i386 system to amd64.  My pbuilder and
  cowbuilder chroots are still i386.  This setup fails to build when it
  could and should succeed.

  dpkg-deb: building package `gjots2' in `../gjots2_3.0.1-0rl3_all.deb'.
   dpkg-genchanges  >../gjots2_3.0.1-0rl3_i386.changes
  dpkg-genchanges: including full source code in upload
   dpkg-source --after-build gjots2-3.0.1
  dpkg-buildpackage: full upload (original source is included)
  I: copying local configuration
  E: Missing changes file: /home/rolf/pbuilder/buildplace/19548/build/gjots2_3.0.1-0rl3_amd64.changes
  I: unmounting dev/ptmx filesystem
  I: unmounting dev/pts filesystem
  I: unmounting dev/shm filesystem

  Notice how gjots2_3.0.1-0rl3_i386.changes but the amd64 version is the
  one being looked for.  This fails and thus the build fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1762890/+subscriptions