Bug#770734: systemd: FTBFS in environment with all packages rebuilt locally

[Sjoerd Simons]

On Sat, Apr 04, 2015 at 07:48:28AM -0700, Daniel Schepler wrote:
> On Wed, Jan 21, 2015 at 8:04 AM, Michael Biebl <biebl at debian.org> wrote:
> 
> > Hi Daniel,
> >
> > Am 23.11.2014 um 19:02 schrieb Daniel Schepler:
> >
> > > I can't reproduce this with a vanilla pbuilder setup, so I'm not sure
> > what's
> > > causing the difference between the two builds.
> >
> > Can you provide any steps how we can reproduce the issue?
> > Does this problem happen with a fresh checkout of the sources, i.e. when
> > you run "apt-get source -b systemd"?
> >
> 
> I finally tracked down a simple way to reproduce the build failure (all in
> a pbuilder login session with the sources line uncommented in
> /etc/apt/sources.list):
> 1. mkdir /tmp/intltool; cd /tmp/intltool; apt-get build-dep intltool
> --no-install-recommends; apt-get source -b intltool
> 2. dpkg -i intltool_*.deb; apt-get -f install --no-install-recommends
> 3. mkdir /tmp/systemd; cd /tmp/systemd; apt-get build-dep systemd
> --no-install-recommends; apt-get source -b systemd
> 
> The strange thing is: the file contents of the newly built intltool package
> and the official intltool package are identical.  About the only difference
> I can see between them is in the file timestamps.

I've just hit the issue on a rebuild we're doing for a derivative. The problem
isn't intltool, it's that autools want to rebuild
org.freedesktop.hostname1.policy due to intltool-merge now being more recent
then the policy file in the source tarball. 

Remaking the policy file fails because there is no src/hostname directory in
the out-of-tree build... In turn the reason there isn't a src/hostname
directory is because we configure with --disable-dependency-tracking
(dh_auto_configure default as it's meant to speed up one-time builds).. Lovely.

I'm having a look whether i can fix upstreams autofoo to make this work
properly.

  Sjoerd