Enabling -ffile-prefix-map by default

[Vagrant Cascadian]

On 2020-06-13, Holger Levsen wrote:
> On Fri, Jun 12, 2020 at 02:27:50PM -0700, Vagrant Cascadian wrote:
>> I've pushed to git:
>>   https://salsa.debian.org/qa/jenkins.debian.net/-/commit/f2a447eacfe375951476f369c8b61f02891d97c7
>
> cool, thanks.
>  
>> Refreshing my memory on how to deploy it by reading the docs... once
>> that's done, we can reschedule builds for affected packages.
>
> $ git push
> $ ./deploy_jdn all

>
> (the latter command just like the git push has to be run from inside the
> jdn.git)
>
> I've did this now.

Thanks!

We've got some updated numbers now!

unstable (with reproducible=+all):

  15 FTBFS packages in unstable/amd64:

     analitza firmware-microbit-micropython grantlee5 ignition-common
     kalarmcal kcodecs kdeclarative kookbook kparts libkgapi
     massif-visualizer okteta scram seqan tellico

bullseye (with reproducible=+all,-fixfilepath after some builds have
been resceduled):

  5 FTBFS packages in bullseye/amd64:

    grantlee5 ignition-common kalarmcal kcodecs tellico

Some of those (e.g. firmware-microbit-micropython) are not in bullseye
at all.

I've rescheduled a few of them again, just to be sure they were built
with -fixfileprefix in bullseye.

Many of them appear to go from FTBFS to reproducible, FWIW.

So we're looking at something in the order of 10 packages that FTBFS
because of this build flag alone that we've identified.

The "knotifications" package is tagged with this issue but builds
reproducibly in all cases, so it's possible it includes a fix or
workaround that might also be applicable for the others?


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/reproducible-builds/attachments/20200616/eb6af7c6/attachment.sig>